[
https://issues.apache.org/jira/browse/SOLR-14040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053036#comment-17053036
]
David Smiley commented on SOLR-14040:
-------------------------------------
> But it affected a small subset of users. Now, we have implemented it for
> cloud, it can potentially affect a vast majority of users (if they use it ) .
Because it's opt-in and it's has been a secret feature still... sorry I just
don't see the severity that you see. Any way, how exactly would you propose
dealing with this in the immediate term -- for 8.5? I don't think you mean to
revert the change in this commit because the feature remains for standalone --
and hence I think we're having the discussion on the wrong issue; should be the
linked SOLR-14232.
> solr.xml shareSchema does not work in SolrCloud
> -----------------------------------------------
>
> Key: SOLR-14040
> URL: https://issues.apache.org/jira/browse/SOLR-14040
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Blocker
> Fix For: 8.5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> solr.xml has a shareSchema boolean option that can be toggled from the
> default of false to true in order to share IndexSchema objects within the
> Solr node. This is silently ignored in SolrCloud mode. The pertinent code
> is {{org.apache.solr.core.ConfigSetService#createConfigSetService}} which
> creates a CloudConfigSetService that is not related to the SchemaCaching
> class. This may not be a big deal in SolrCloud which tends not to deal well
> with many cores per node but I'm working on changing that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
