[
https://issues.apache.org/jira/browse/SOLR-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729891#comment-13729891
]
Erick Erickson commented on SOLR-4779:
--------------------------------------
I may be able to get to this Real Soon Now, but not before we get named config
sets in place.
But the situation will be awkward. There was a discussion about how sharing a
solrconfig object is fraught with all kinds of places to screw it up. So now
imagine we go ahead and integrate sharing the schema with config sets. Now
changing a config set does what? Reloads the schema file but not the solrconfig
file? Spins through all the open cores and causes them to reload (easy, but
yuuuuck). And how would all that get triggered in the first place?
> 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: 4.4, 5.0
> 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]
