What to do after editing eZFind/solR configuration ?

Monday 18 October 2010 9:11:12 am

Hello,

Can someone validate those steps when modifying ezfind/solr configurations ?

For eZFind :

1. editing ezfind.ini
2. php extension/ezfind/bin/php/updatesearchindexsolr.php -s siteaccess --php-exec=/usr/bin/php

For solR :

1. editing schema.xml (the one loaded for your system either uni or multi-core)
2. removing index datas by : rm -rf ./extension/ezfind/java/solr/data/*
3. restarting solr (debian install script) : /etc/init.d/solr restart

What does ezfindexcontent.php is doing as even when its not running content is indexed when publishing from admin siteaccess ?

EZP is Great

Monday 25 October 2010 4:52:43 am

Further insight:

. content is indexed in realtime when it is edited by default. No need for the ezfindexcontet cronjob. But you can configure eZP to index new in non-realtime mode. It is a parameter in site.ini: DealayedIndexing. When it is enabled, you have to set up the cronjob to periodically index your new contents, or it will never be indexed.

The advantage of non-realtime indexing is that the editing process is slightly faster.

It is also a very good idea to disable realtime indexing when running content import batch scripts.

. after editing schema.xml, it is better if you reindex all of your contents, as some of the changes you have made might need to be taken into account at indexation time, not only at search time. So run again updatesearchindexsolr.php on the eZ side

Principal Consultant International Business
Member of the Community Project Board