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
On Wed, Oct 12, 2011 at 11:28 PM, 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 bel