[
https://issues.apache.org/jira/browse/SOLR-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652686#comment-13652686
]
Steve Rowe commented on SOLR-4779:
----------------------------------
{quote}
bq. (And of course: the question of what happens with mutable schemas when
shared is something that should be considered)
Seems like all cores sharing the same physical file should get the updates.
This should already work in cloud mode, but I have a feeling non-cloud mode
doesn't.
{quote}
Mutable schemas don't work with shared schema in multi-core mode right now. I
need to write tests for that and merge back the (partial and unconnected) code
I had but that got disappeared in Mark Miller's changes to CoreContainer.
bq. It's probably also the case that the schema API should be able to specify a
named config set to operate on.
Can't find the issue now, but somewhere there was a discussion about this, and
I think I suggested REST API URLs like
solr/configs/(name)/schema/(request-path). Then solrconfig access might be
solr/configs/(name)/solrconfig/(request-path).
> 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]
