Re: [VuFind-Tech] Solr 1.4 branch ready ... and spellchecker question

[Demian K. <dem...@vi...>]

Thanks to Greg, I've fixed the buildOnOptimize problem -- the setting was nested in the wrong part of the XML configuration.  I've committed a fix to my branch (r1843) and also merged in all of the latest trunk changes (r1844).  Please take a look if you haven't already and let us know if you run into any problems.

thanks,
Demian

From: Demian Katz
Sent: Friday, November 13, 2009 11:00 AM
To: vuf...@li...
Subject: Solr 1.4 branch ready ... and spellchecker question

Hello again,

Looks like the Solr 1.4 upgrade is pretty much a drop-in operation.  I've established a branch for testing:

https://vufind.svn.sourceforge.net/svnroot/vufind/branches/demian_solr14/

This is exactly the same as trunk, except it contains Solr 1.4, and I've turned on the spellchecker by default.  Please give it a try and let me know if you run into any trouble!  (Note that you'll need to reindex in order to test this due to the Solr version change).

I'm having just one problem so far, and I'm hoping some of the spellcheck experts on this list can help out.

When I turned on the spellcheck options, I activated the buildOnOptimize setting in solrconfig.xml.  However, my spellchecker index does NOT build when I optimize Solr.  I tried using buildOnCommit instead, but that didn't work either.  Right now, I can only seem to get the spellchecker index to build through the manual "&spellcheck.build=true&spellcheck=true on the Solr URL" approach.  I also checked to see if initializing the index through the URL method caused subsequent optimize/commit actions to take effect, but it makes no difference -- as far as I can tell, they never work.

I'm currently performing my commit/optimize actions using the util/suppressed.php script, which is just calling the appropriate methods of the Solr class to post XML commands to Solr's /update/ endpoint.  The actual commits/optimizes themselves are definitely working, but no spellchecker action is resulting.  I can't tell if I'm doing something wrong by missing a detail somewhere (i.e. do I need to add some extra parameter to the update command to activate the spellcheck component?), or if this feature just isn't working right.

Any ideas?

thanks,
Demian