[ https://issues.apache.org/jira/browse/SOLR-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716088#comment-14716088 ]
ASF subversion and git services commented on SOLR-7789: ------------------------------------------------------- Commit 1698072 from gcha...@apache.org in branch 'dev/trunk' [ https://svn.apache.org/r1698072 ] SOLR-7789: fix jira number in CHANGES.txt > Introduce a ConfigSet management API > ------------------------------------ > > Key: SOLR-7789 > URL: https://issues.apache.org/jira/browse/SOLR-7789 > Project: Solr > Issue Type: New Feature > Reporter: Gregory Chanan > Assignee: Gregory Chanan > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org