[
https://issues.apache.org/jira/browse/SOLR-14040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053208#comment-17053208
]
Bruno Roustant commented on SOLR-14040:
---------------------------------------
This is a good opportunity for me to learn how we deal with feature development
and work in progress.
As I understand shared-schema (SolrCloud or not) is still in development and
not documented, still with some limitations/problems. Do we document in the ref
guide features in progress?
Because it seems weird to me to document a limitation in the ref guide for a
feature that is not yet documented as available. If we document the limitation,
shouldn't we also document the feature itself, but actually it is not ready...
difficult. Is there a section specific to "coming" features?
In fact, where do the users learn about this undocumented feature? Directly in
the code? This is where we should explain the current limitations and risks.
> 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
