Erick Erickson created SOLR-13584:
-------------------------------------
Summary: Explore prohibiting aliases and collections from having
the same name.
Key: SOLR-13584
URL: https://issues.apache.org/jira/browse/SOLR-13584
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Erick Erickson
Allowing aliases and collections to have the same name is fragile and a
potentially a data issue. I'll link in a few JIRAs illustrating this and one at
least where the discussion gets long.
Straw-man proposal to start things off.
Deprecate this ability now, and enforce it in 9.0.
We have to provide a graceful way for users to get themselves out of the
following currently-possible use-case.
* a collection C1 is created and all the front-end uses it.
* users want to atomically switch to a new collection for various reasons
* users create C2 and test it out.
* users create an alias C1->C2
Let's discuss.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
