>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:
>t
: >* What is the motivation/use case for editing the schema at runtime?
: (I'm not suggesting there aren't good ones, just curious)
:
: to add new fields on the fly without having any search downtime
i haven't read anything in the jira issue this refrences, but in instances
where reliability and
>I haven't looked at the patch, but have a couple questions:
>* What is the motivation/use case for editing the schema at runtime? (I'm not
>suggesting there aren't good ones, just curious)
to add new fields on the fly without having any search downtime
>* Would changes be saved?
the patch as
[
https://issues.apache.org/jira/browse/SOLR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505950
]
Ryan McKinley commented on SOLR-265:
I haven't looked at the patch, but have a couple questions:
* What is the moti
[
https://issues.apache.org/jira/browse/SOLR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505938
]
Will Johnson commented on SOLR-265:
---
After doing some more thinking about the issue after I submitted the
patch I agr
[
https://issues.apache.org/jira/browse/SOLR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505927
]
Yonik Seeley commented on SOLR-265:
---
Doesn't this have thread-saftey and unsolvable consistency issues?
It doesn't se
