[ 
https://issues.apache.org/jira/browse/SOLR-14040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050542#comment-17050542
 ] 

Noble Paul commented on SOLR-14040:
-----------------------------------

bq.This shortcoming is not new; it was here before I SolrCloud-enabled 
shareSchema. 

You are right. This problem existed. 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 ) .

bq.  shareSchema is undocumented, and undocumented is basically the same as 
experimental,

I'm not sure if {{undocumented = experimental}} . We should have a proper way 
to communicate an existing feature as potentially buggy/use with care

> 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

Reply via email to