The problem you're seeing is SolrMarc-related and affects all versions of VuFind regardless of Solr version. It's not directly related to the Solr 1.4 branch.
The vufind_config.properties file that used to be packaged in the jar file is now the import/import.properties file (actually, the import/import.properties existed even when vufind_config.properties was still inside the jar -- it just used to act as an override rather than being the only version that exists). All of the scripts in the import/bin directory seem to assume that the properties files are embedded in the jar, and I'm guessing that they need to be updated to work correctly with external configuration files. I recently posted about this on the solrmarc-tech list, but nobody has responded yet.
Until this gets sorted out on the SolrMarc side, I think the best option is to ignore all the import/bin scripts.
However, getting back to your original problem of a few days ago, it looks like the easiest way to get SolrMarc to optimize the index after an import is to add this line to the import/import.properties file:
solr.optimize_at_end = true
I just tried this on my test server and it worked.
Let me know if there are any other functions of the import/bin scripts that you actually need -- hopefully we can find workarounds for them if we can't get working versions of the scripts in a timely fashion.
From: Barnett, Jeffrey [mailto:jeffrey.barnett@...]
Sent: Friday, November 13, 2009 3:08 PM
To: Demian Katz; vufind-tech@...
Subject: RE: Solr 1.4 branch ready ... and spellchecker question
I doesn't work for me...
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Caused by: java.lang.IllegalArgumentException: Fatal error: Unable to find specified properties file: vufind_config.properties
I looked at import/bin/Generic_VuFind_SolrMarc.jar and the config file is no longer packaged there, but neither is it anywhere else I can find. Where should it be and/or where should I point showconfig to?
From: Demian Katz [mailto:demian.katz@...]
Sent: Friday, November 13, 2009 11:00 AM
Subject: [VuFind-Tech] Solr 1.4 branch ready ... and spellchecker question
Looks like the Solr 1.4 upgrade is pretty much a drop-in operation. I've established a branch for testing:
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.