[
https://issues.apache.org/jira/browse/SOLR-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652611#comment-13652611
]
Hoss Man commented on SOLR-4779:
--------------------------------
it's important to remember what exactly shareSchema="true" means under the hood.
functiaonlly the effect was that you got the exact same IndexSchema object for
all cores whose schema.xml path was the same -- it helps reduce the memory
overhead and speeds up the loading of cores in situations where you have a lot
of cores using identical schemas.
re-using config sets in SolrCloud may be a viable replacement for sharing
schemas such that the config option is no longer needed -- but the question
should still remain whether that will still support the optimization of having
a single IndexSchema object for each core that re-uses the same config set.
(And of course: the question of what happens with mutable schemas when shared
is something that should be considered ... i have no idea what happens today)
> 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]
