[
https://issues.apache.org/jira/browse/SOLR-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944033#comment-14944033
]
Gregory Chanan commented on SOLR-8054:
--------------------------------------
Ok, from discussing with [~anshumg] in SOLR-6736 it sounds like we are going to
use that jira for modification and this JIRA for GET.
I do not currently have a patch for GET. As I wrote above, I think there are
two separate steps here (that could be separate jiras, but should have a
sensible API between them):
1) Config/Schema API equivalents
2) File-based APIs
My plan is to start work on 1) first, someone can take up 2) or I can work on
it after 1). But let's figure out a sensible API before we commit anything.
> Add a GET command to ConfigSets API
> -----------------------------------
>
> Key: SOLR-8054
> URL: https://issues.apache.org/jira/browse/SOLR-8054
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
>
> It would be useful to have a command that allows you to view a ConfigSet via
> the API rather than going to zookeeper directly. Mainly for security
> reasons, e.g.
> - solr may have different security requirements than the ZNodes e.g. only
> solr can view znodes but any authenticated user can call ConfigSet API
> - it's nicer than pointing to the web UI and using the zookeeper viewer,
> because of the same security concerns as above and that you don't have to
> know the internal zookeeper paths.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
