[
https://issues.apache.org/jira/browse/SOLR-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188551#comment-17188551
]
Ilan Ginzburg commented on SOLR-14794:
--------------------------------------
I've reverted this commit. Will resolve this issue.
Once/if we decide to use {{solr.xml}} as a configuration source for commands,
will implement your improvement suggestion. Thanks.
> Pass global cloud configuration to Collection API command execution
> -------------------------------------------------------------------
>
> Key: SOLR-14794
> URL: https://issues.apache.org/jira/browse/SOLR-14794
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: config-api, SolrCloud
> Affects Versions: master (9.0)
> Reporter: Ilan Ginzburg
> Assignee: Ilan Ginzburg
> Priority: Major
> Labels: collection-api, configuration, solr.xml, solrcloud
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Overseer has access to {{CloudConfig}} (a {{SolrCloud}} specific
> configuration subsection of {{solr.xml}}).
> The replacement of the Autoscaling framework in 9.0 (being worked on in
> SOLR-14613) requires access to SolrCloud configuration for placement
> decisions.
> This Jira is about making {{CloudConfig}} available to Collection API (or
> Config Set API) command execution in general.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
