[
https://issues.apache.org/jira/browse/SOLR-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295829#comment-16295829
]
Peter Rusko commented on SOLR-8389:
-----------------------------------
This patch above is just providing a way for properties to be assigned to
collections. It is pretty generic at the moment, the value can be anything, so
you can assign any JSON value you want, it won't require a target collection to
be set. The interpretation of the value comes down to the code reading the
value.
It looks like it's missing two things. None of those seem to be important for
the first iteration to me. One is the ability to assign a value at the
collection creation time and the other is a support of a property value
validator, which could check that the assigned value has certain fields for
instance.
Is it okay if we merge this patch as it is so far, provided someone can review
it? Then I, or someone else with better ideas can add the two missing pieces
above later, if they are needed.
> Convert CDCR peer cluster and other configurations into collection properties
> modifiable via APIs
> -------------------------------------------------------------------------------------------------
>
> Key: SOLR-8389
> URL: https://issues.apache.org/jira/browse/SOLR-8389
> Project: Solr
> Issue Type: Improvement
> Components: CDCR, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Attachments: SOLR-8389.patch
>
>
> CDCR configuration is kept inside solrconfig.xml which makes it difficult to
> add or change peer cluster configuration.
> I propose to move all CDCR config to collection level properties in cluster
> state so that they can be modified using the existing modify collection API.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
