Hi, To be able to do a true hot deploy of newer schema without reindexing, you must carefully see to that none of your changes are breaking changes. So you should test the process on your development machine and make sure it works. Adding and deleting fields would work, but not changing the field-type or analysis of an existing field. Depending on from/to version, you may want to keep the old schema-version number.
The process is: 1. Deploy the new schema, including all dependencies such as dictionaries 2. Do a RELOAD CORE http://wiki.apache.org/solr/CoreAdmin#RELOAD My preference is to do a more thorough upgrade of schema including new functionality and breaking changes, and then do a full reindex. The exception is if my index is huge and the reason for Solr upgrade or schema change is to fix a bug, not to use new functionality. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com On 24. jan. 2012, at 01:51, roz dev wrote: > Hi All, > > I need community's feedback about deploying newer versions of solr schema > into production while existing (older) schema is in use by applications. > > How do people perform these things? What has been the learning of people > about this. > > Any thoughts are welcome. > > Thanks > Saroj
