[
https://issues.apache.org/jira/browse/SOLR-11624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249850#comment-16249850
]
Cassandra Targett commented on SOLR-11624:
------------------------------------------
bq. The principle of least surprise comes in to play here. Once a configset
exists in ZooKeeper, don't change it unless I tell you to. End of story.
I'm +1 on this idea. I too don't understand the confusion and complication
around just not overwriting an existing configset when one already exists that
matches the name of the collection.
bq. The idea of that whole exercise (default configset) was to not need the
user to be aware of the concept of configsets.
In my mind, the goal was not to remove the need for new users to ever learn of
the concept of configsets. It was to reduce the barrier of having to learn
*everything* about configsets before you can even remotely start with Solr.
(Actually, to be more precise, it was to fix the scenario where a new user
fires up the Admin UI and clicks a button to create a collection that 100% of
the time fails with a cryptic-to-them error message.) What we've done here is
make something that should be a convenience into a poor experience for anyone
who knows what they are doing. We must find the balance between these things.
The way this currently works has not, in fact, simplified the whole story at
all, just changed where surprising and annoying behavior occurs. Further, I
don't find where this behavior is described in the Ref Guide, so there isn't
even any explanation for users to understand what new implicit rules they're
expected to know before trying to use it.
> _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]
