[SOLR-13584] Explore prohibiting aliases and collections from having the same name.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: Erick Erickson
• Created: 28/Jun/19 15:28
• Updated: 04/Dec/19 19:27
• Resolved: 04/Dec/19 19:27

Description

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.

Issue Links

• duplicates: SOLR-11488 Do not allow collections and aliases to have the same name
• is related to: SOLR-13583 Impossible to delete a collection with the same name as an existing alias
• is related to: SOLR-13122 Ability to query aliases in Solr Admin UI