[
https://issues.apache.org/jira/browse/SOLR-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652867#comment-13652867
]
Erick Erickson commented on SOLR-4779:
--------------------------------------
bq: It would be nice if all cores sharing a named config would also share the
same exact schema object.
Right. That's the intent. But I was assuming that changes would require a
constructing a new IndexSchema object. But cores all have a reference to
whatever schema object they had when created. So 10 cores could be sharing the
same object, but then the schema changes and we create a new one. For some time
we have two schema objects hanging around and as cores reload they'd get the
new one.
But that just proves I should look through the code first. SolrCore has a
setLatestSchema method that replaces the current schema with a new one. So it
looks like the stage is set to just spin through the cores and replace the
current schema with the new one in the cache when it changes. Then it should
work like you're saying.
Glad you pointed that out...
> Deprecate shareSchema in favor of sharing named config sets
> -----------------------------------------------------------
>
> Key: SOLR-4779
> URL: https://issues.apache.org/jira/browse/SOLR-4779
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 5.0, 4.4
> Reporter: Erick Erickson
> Assignee: Erick Erickson
>
> While working on SOLR-4478 it occurred to me that sharing schemas should be
> superseded by sharing named config sets. I pinged the dev list and there's
> enough interest in this that a JIRA is in order to continue the discussion.
> This _may_ just happen as part of SOLR-4478.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
