[
https://issues.apache.org/jira/browse/SOLR-15258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415221#comment-17415221
]
David Smiley commented on SOLR-15258:
-------------------------------------
Yep. I think ZkContainer.initZooKeeper should not be referring to
ConfigSetService at all. Instead, later when ConfigSetService is initialized,
it can check if bootstrap_conf is set. Come to think of it, this config
bootstrapping altogether doesn't seem to belong in ZkContainer either
(separation of concerns) although there is some entanglement with the logic
there, so it'll take some care to separate.
> ConfigSetService: add CRUD operations, subsume ZkConfigManager
> ---------------------------------------------------------------
>
> Key: SOLR-15258
> URL: https://issues.apache.org/jira/browse/SOLR-15258
> Project: Solr
> Issue Type: Improvement
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Fix For: main (9.0)
>
> Time Spent: 9.5h
> Remaining Estimate: 0h
>
> Increase the scope of ConfigSetService with CRUD operations and anything else
> so that it can be the one place to go for anything ConfigSet related. This
> should be easier to understand/maintain, and also improve the efficacy of the
> plug-ability of ConfigSetService.
> It's likely ZkConfigManager will disappear, with most of its functionality
> moving into CloudConfigSetService (ZK). A number of places in SolrCloud use
> ZkConfigManager that will change to use the ConfigSetService instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
