I would consider "shadow" cores for this use case. Say you have coreA live, and a coreB which is not live.
Then, upgrade schema in coreB, clear the index, feed all content, test that it works ok, and finally, do a CORE.SWAP /solr/admin/cores?action=SWAP&core=coreA&other=coreB - See http://wiki.apache.org/solr/CoreAdmin#SWAP or alternatively do the name swap in your frontend and feeder and keep track of whether A or B is live. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com On 12. okt. 2011, at 19:58, Ben Hsu wrote: > Hello Solr users. > > My organization is working on a solr implementation with multiple cores. I > want to prepare us for the day when we'll need to make a change to our > schema.xml, and roll that change into our production environment. > > I believe we'll need to perform the following steps: > # delete all our documents > # update the schema.xml in all our cores > # rebuild the index from the source data. > > Have any of you done this? What has your experience been?
