[
https://issues.apache.org/jira/browse/SOLR-7507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534111#comment-14534111
]
Noble Paul commented on SOLR-7507:
----------------------------------
I understand your usecase but I don't think this warrants a new feature. We
have a proliferation of configurable things. This leads to too much confusion.
Implementing this is not as simple as your patch. All nodes need to watch for
changes of this properties and update themselves .
bq:why the solrcore.properties are not loaded from zookeeper
solrcore.properties is a legacy thing and I don't expect that feature is very
relevant in SolrCloud. Actually we don't want users to be conscious about the
cores at all when they are using cloud. if at all we should have something like
that , it should be called collection.properties
Your best bet is to use one configset per collection and to use userprops for
this. We already have a well defined API and documentation for the same
> Collection specific config for SolrCloud
> ----------------------------------------
>
> Key: SOLR-7507
> URL: https://issues.apache.org/jira/browse/SOLR-7507
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 5.1
> Reporter: Markus Heiden
> Priority: Minor
> Labels: patch
> Attachments: SolrCloudCollectionConfig.patch
>
>
> SolrCloud uses the collection abstraction and propagates to not think of
> cores. But currently the collection properties are just stored as core
> properties of the created cores. These won't get propagated to new nodes
> automatically. This is counter-intuitive.
> This patch adds the possibility to add collection specific config files.
> These are put under the collection node in zookeeper. The resolution order
> for config file accesses is now: 1) collection node, 2) config set node, 3)
> classpath. Notice that the filesystem fallback (default:
> conf/solrcore.properties) has been removed for SolrCloud mode.
> This allows for having one generic config set being used for different
> collections which just differ in their solrcore.properties. Furthermore the
> solrcore.properties need no more to exist in the filesystem but are
> distributed via zookeeper as it should be (IMO).
> If you like this patch, I will add a patch for ZkCLI which allows the upload
> of config files for a collection in the linkconfig command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
