[
https://issues.apache.org/jira/browse/SOLR-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304519#comment-16304519
]
Amrit Sarkar commented on SOLR-8389:
------------------------------------
I would need some advice on designing the new APIs for CDCR specially adding /
modifying target configs.
this is sample API I have designed for now which is very ineffective:
{{/cdcr/action=MODIFY&replica.zkhost=zkhost:zkpost/chroot&replica.target=targetColName}}
and add them sequentially to add all the target collection information ONE BY
ONE.
*Should I configure JSON payload as request or use V2 API to pass multiple
target configs at once?* I know this configuration will be passed just one, and
wouldn't hurt if target configs be passed one by one.
Looking forward to suggestions, I am still cleaning code to support this and
then will start modifying tests around all components.
> 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, 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
