[ 
https://issues.apache.org/jira/browse/SOLR-11624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248351#comment-16248351
 ] 

Ishan Chattopadhyaya commented on SOLR-11624:
---------------------------------------------

Here's the reason behind putting in that change:

The idea of that whole exercise (default configset) was to not need the user to 
be aware of the concept of configsets. In that situation, here's a typical 
situation that a user (who isn't aware of the concept of configsets) would be 
faced with, if the current behavior were not to be there: a) user creates a 
collection without specifying a configset, b) makes some changes to 
schema/configs using APIs, c) he's unhappy with how things turned out and 
deleted that collection and re-created it, d) instead of starting from scratch 
(default configset), as he was hoping, he is at the same place where he left 
off before deleting the collection.

Overwriting any existing configset results in a climate of least surprises for 
a new user. However, those who understand concepts of configsets can always 
specify a configset name while creating his collections. IMHO, we should keep 
the current behavior. But, as I mentioned before, if there's consensus on 
switching back to previous behavior, I can work on bringing it back.

> _default configset overwrites a a configset if collection.configName isn't 
> specified even if a confiset of the same name already exists.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-11624
>                 URL: https://issues.apache.org/jira/browse/SOLR-11624
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 7.2
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>         Attachments: SOLR-11624.patch
>
>
> Looks like a problem that crept in when we changed the _default configset 
> stuff.
> setup:
> upload a configset named "wiki"
> collections?action=CREATE&name=wiki&.....
> My custom configset "wiki" gets overwritten by _default and then used by the 
> "wiki" collection.
> Assigning to myself only because it really needs to be fixed IMO and I don't 
> want to lose track of it. Anyone else please feel free to take it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to