[
https://issues.apache.org/jira/browse/SOLR-12188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826782#comment-16826782
]
Ishan Chattopadhyaya commented on SOLR-12188:
---------------------------------------------
bq. The default configset is trappy enough since it defaults to schemaless, I
kind of like that it is in people's faces. I agree it's inconsistent, but am
happy to live with that. I wouldn't veto the change, but wanted to mention
it....
The intent of the move to make configset optional was to ensure that it stays
out of users' way as an internal detail. However, since it defaults to
schemaless, how about we add a warning (popup) at the time of creation that
this shouldn't be used for production because schemaless is not recommended
(similar to what the API warns)?
> 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.4
> Reporter: Munendra S N
> Assignee: Ishan Chattopadhyaya
> 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
