lucene-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (SOLR-13584) Explore prohibiting aliases and collections from having the same name.
Date Wed, 04 Dec 2019 19:28:00 GMT

     [ https://issues.apache.org/jira/browse/SOLR-13584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Erick Erickson resolved SOLR-13584.
-----------------------------------
    Resolution: Duplicate

Done, thanks [~ctargett] for pointing this out.

> 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
>            Reporter: Erick Erickson
>            Priority: Major
>
> 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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org


Mime
View raw message