Hi,
As suggested by the Solr Enterprise book, I have separate strategies for
updating the solr core (e.g. blah) when I need to do incremental
updates(every day) VS create a fresh index from scratch(once in a 4 months).
Assuming that the dataDir for the core "blah" is /home/blah/data/defaultData
in the solr.xml.
For creating the full index for my core every quarter from scratch:
- I create a new core e.g. "blahNov2012" using admin url with option
action=CREATE and I give it a new dataDir property e.g.
/home/blah/data/Nov2012.
- I do a full import on blahNov2012 to populate the new core "blah-Nov2012"
and test it.
- If all is good, I run the admin url with option action=SWAP to swap (blah
with blahNov2012).
- Since I have persistent="true" in the solr.xml, it updates the dataDir for
the core "blah" to point to the new directory /home/blah/data/Nov2012.
<?xml version="1.0" encoding="UTF-8" ?>
<solr sharedLib="lib" persistent="true">
<property name="enable.slave" value="false"/>
<property name="enable.master" value="true"/>
<cores adminPath="/admin/cores">
<core name="blah" instanceDir="blah/" dataDir="/home/blah/data/Nov2012">
</core>
</cores>
</solr>
My first question: is this the pattern most people use to create fresh index
(e.g. create a new tmp core, test, and swap).
My second question is if I need to make further unrelated changes the
solr.xml in next releases and I must update the solr.xml on the production
system, I need to manually change the "blah"'s data directory from
"/home/blah/data/defaultData" to "/home/blah/data/Nov2012". Is that what
needs to be done? Do people automate this step somehow in their production
releases..?
-maneesha
--
View this message in context:
http://lucene.472066.n3.nabble.com/Management-of-solr-xml-on-master-server-tp4016570.html
Sent from the Solr - User mailing list archive at Nabble.com.
