[
https://issues.apache.org/jira/browse/SOLR-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941964#comment-14941964
]
Gregory Chanan commented on SOLR-8054:
--------------------------------------
I started prototyping this out. I think there are potentially multiple tasks
here:
1) Config API / Schema API equivalents for ConfigSets
See SOLR-7570 for the genesis of this; in short, the collection-based Config
API and Schema APIs should not modify the underlying ConfigSet. It makes
sense, then, to have GET-able Config API/Schema APIs that are specific to the
ConfigSet because:
a) these may be different from the Collection-Config representation
b) you may not have a collection using the ConfigSet currently in a "template"
world (SOLR-5955).
Having PUT/POST-able ConfigSet-specific APIs is an open question IMO.
2) "Raw" File based view
I'm thinking an http equivalent for "ZkCli -cmd DOWNCONFIG". The motivation is
a subset of the motivation for a ConfigSet API as a whole, namely:
m1) Doesn't require zookeeper access (which may not be available)
m2) Can use the same authentication/authorization mechanisms as the rest of Solr
m3) Doesn't require a collection to be instantiated (as today via the ShowFile
API)
There is a limitation due to http as compared to the ZkCli equivalent, namely
that you can't "download" multiple files in a single GET request, see
http://stackoverflow.com/questions/1041542/how-to-download-multiple-files-with-one-http-request.
So we'd have to do one of the following:
o1) zip up the ConfigSet
o2) require the client to go file-by-file like the ShowFile API today
o3) invent/use our own format that has "file breaks" within a single response
I'm not sure the effort here is worth it, considering (I hope) the future is
API-based like the Config/Schema API, not File-based. But it does at least
seem useful until we are in a world where the majority are using the APIs. As
for the options, I don't like o1). I don't have a strong preference for o2) vs
o3), although I think I'd lean slightly to o3) just to be able to reduce the
number of http calls required to download a config.
Thoughts?
> 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]
