[
https://issues.apache.org/jira/browse/SOLR-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367882#comment-16367882
]
Amrit Sarkar commented on SOLR-8389:
------------------------------------
Hi [~prusko],
I apologise I should have put down the details on how we are approaching on
this JIRA with your patch. We are leveraging the patch provided by you to
improve the CDCR configuration but obviously it has other use-cases and I see
Tomas is reviewing on SOLR-11960. Well if SOLR-11960 goes in, then yes, I
believe too we don't need a seperate cdcr.json, hence I will wait for others in
the community to weigh in on agreeing to the common properties having cdcr ones.
> 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
> Priority: Major
> Attachments: SOLR-8389.patch, SOLR-8389.patch, SOLR-8389.patch,
> SOLR-8389.patch, SOLR-8389.patch, SOLR-8389.patch, SOLR-8389.patch,
> SOLR-8389.patch, SOLR-8389.patch, SOLR-8389.patch, SOLR-8389.patch, Screen
> Shot 2017-12-21 at 5.44.36 PM.png
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
