[
https://issues.apache.org/jira/browse/SOLR-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652674#comment-13652674
]
Erick Erickson commented on SOLR-4779:
--------------------------------------
@Hoss:
Yep, what I'm trying to do is share the same object, in this case both the
schema and config file. It actually takes quite a while to load the config.
What's not clear to me at all is whether the SolrConfig object is shareable,
but I'm looking at that.
@Yonik:
All things being equal, all cores sharing the config set would get the updates
to both schema and core, but probably not until they were reloaded if they were
currently loaded when the change was made.
@Shawn:
Really good question. I think the answer would be that there would temporarily
be two objects, each core would have a reference to an underlying object that
would eventually go away after the last core sharing that config set was
reloaded.
> 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]
