>i haven't read anything in the jira issue this refrences, but in instances >where reliability and uptime are of high concern, you'll typically have a >master/multi-slave setup with the slaves sitting behind a load balancer >-- in that configuration, you can deploy any change to your schema by:
>this process results in 0 downtime for any schema.xml change, regardless >whether the changes require rebuilding your index. True, but that implies indexing downtime which is also bad. Also, the master/slave setups kill indexing latency which is my primary concern and the reason I went with solr to begin with. also while you're suggested steps work they're a bit heavy on the operations side compared to a client's ability to add a field by hitting a url. >if you change/add a copyField declaration, you'll need to reindex ... >copyField is evaluated when a document is being indexed. True, but not if you haven't fed any data into that copy field yet. Ie 'from now on' I want all data from field x copied into field y. - will
