On 03/28/2010 05:43 PM, Blargy wrote:
Thanks that makes perfect sense for solrconfig.xml however I dont see that sort of functionality for solr.xml.Im guessing Ill need to manage 2 different versions of solr.xml Version 1 master <solr persistent="true" sharedLib="lib"> <cores adminPath="/admin/cores" shareSchema="true"> <core name="items-live" instanceDir="items" default="true" dataDir="data/core0"/> <core name="items-offline" instanceDir="items" default="true" dataDir="data/core1"/> </cores> </solr> Version 2 slave <solr persistent="false" sharedLib="lib"> <cores adminPath="/admin/cores" shareSchema="true"> <core name="items" instanceDir="items" default="true"> </cores> </solr> And my app will always be pointing to http://slave-host:8983/solr/items This isnt the biggest deal but if there is a better/alternative way I would love to know.
Hmmm...but isn't your slave on a different machine? Every install is going to need a solr.xml, no way around that (other than removing the solr.xml and doing all multicore stuff programmaticly :) ).
Mark, I see you work for LucidImagination. Does the Lucid solr distribution happen to come with Solr-236 patch (Field Collapsing). I know it has some extras thrown in there but not quite sure of the exact nature of it. Im already using the LucidKStemmer ;)
No, no Field Collapsing in the Lucid Dist - it will make it into Solr eventually tough.
-- - Mark http://www.lucidimagination.com
