[
https://issues.apache.org/jira/browse/SOLR-12188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427070#comment-16427070
]
Munendra S N commented on SOLR-12188:
-------------------------------------
[^SOLR-12188.patch]
With this patch, CREATE collection in Admin UI would mimic CREATE API behavior
i.e, if configSet is not passed then mutable configSet with suffix
*.AUTOCREATED* would be created.
But when _default is specified as configSet then no new mutable configSet is
not created. In this case, collections would share the _default configSet.
Should this also be changed?
> Inconsistent behavior with CREATE collection API
> ------------------------------------------------
>
> Key: SOLR-12188
> URL: https://issues.apache.org/jira/browse/SOLR-12188
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI, config-api
> Affects Versions: 7.2
> Reporter: Munendra S N
> Priority: Major
> Attachments: SOLR-12188.patch
>
>
> If collection.configName is not specified during create collection then
> _default configSet is used to create mutable configSet (with suffix
> AUTOCREATED)
> * In the Admin UI, it is mandatory to specify configSet. This behavior is
> inconsistent with CREATE collection API(where it is not mandatory)
> * Both in Admin UI and CREATE API, when _default is specified as configSet
> then no mutable configSet is created. So, changes in one collection would
> reflect in other
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
