[
https://issues.apache.org/jira/browse/SOLR-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723816#comment-14723816
]
Gregory Chanan commented on SOLR-7789:
--------------------------------------
bq. Is there a LIST option? I'd love to use this in the admin UI and would
rather avoid having to do Zookeeper lookups in order to make it work. All I
need (initially) is to be able to get a list of configset names.
There is not currently, but that's a good idea. I filed SOLR-7995 to add it.
bq. I wish there are a few examples added in the description so that I don't
have to go through the tests to figure out how it looks like to a user
I'm happy to turn the first comment into a page on the cwiki. I modeled that
comment after the
https://cwiki.apache.org/confluence/display/solr/Collections+API page so it
would be easy to do. Is it okay to add the page now, even though there is no
release with this feature yet? That seems like a more fruitful place to have
discussions about making it easier to understand for end users.
> Introduce a ConfigSet management API at /admin/configs
> ------------------------------------------------------
>
> Key: SOLR-7789
> URL: https://issues.apache.org/jira/browse/SOLR-7789
> Project: Solr
> Issue Type: New Feature
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
> Fix For: Trunk, 5.4
>
> Attachments: SOLR-7789.patch, SOLR-7789.patch, SOLR-7789.patch,
> SOLR-7789.patch, SOLR-7789.patch
>
>
> SOLR-5955 describes a feature to automatically create a ConfigSet, based on
> another one, from a collection API call (i.e. one step collection creation).
> Discussion there yielded SOLR-7742, Immutable ConfigSet support. To close
> the loop, we need support for a ConfigSet management API.
> The simplest ConfigSet API could have one operation:
> create a new config set, based on an existing one, possible modifying the
> ConfigSet properties. Note you need to be able to modify the ConfigSet
> properties at creation time because otherwise Immutable could not be changed.
> Another logical operation to support is ConfigSet deletion; that may be more
> complicated to implement than creation because you need to handle the case
> where a collection is already using the configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
