[jira] [Comment Edited] (SOLR-7507) Collection specific config for SolrCloud

["Markus Heiden (JIRA)" <ji...@apache.org>]

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

Markus Heiden edited comment on SOLR-7507 at 5/7/15 3:21 PM:
-------------------------------------------------------------

No, not as it should be: If you create a collection the custom properties have to be specified each via a parameter in the CREATE-URL. This is annoying, if you have many of them. Furthermore these properties are stored only in the core.properties of the created core and not in zookeeper. So if you create new nodes for a collection, you have to provide the same properties over and over again -> error-prone.

What we try to achieve is to have one config set for all of our collections which just differ in their properties. Currently this is only possible if we manually create the cores and provide a conf/solrcore.properties in the filesystem for each core. We don't like the brute force alternative: Avoiding properties by multiplying our config sets.


was (Author: markus_heiden):
No, not as it should be: If you create a collection the custom properties have to be specified each via a parameters in the CREATE-URL. This is annoying, if you have many of them. Furthermore these properties are stored only in the core.properties of the created core and not in zookeeper. So if you create new nodes for a collection, you have to provide the same properties over and over again -> error-prone.

What we try to achieve is to have one config set for all of our collections which just differ in their properties. Currently this is only possible if we manually create the cores and provide a conf/solrcore.properties in the filesystem for each core. We don't like the brute force alternative: Avoiding properties by multiplying our config sets.

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org