You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Andrzej Bialecki (JIRA)" <ji...@apache.org> on 2019/07/02 00:25:00 UTC
[jira] [Updated] (SOLR-13583) Impossible to delete a collection
with the same name as an existing alias
[ https://issues.apache.org/jira/browse/SOLR-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrzej Bialecki updated SOLR-13583:
-------------------------------------
Attachment: SOLR-13583.patch
> Impossible to delete a collection with the same name as an existing alias
> -------------------------------------------------------------------------
>
> Key: SOLR-13583
> URL: https://issues.apache.org/jira/browse/SOLR-13583
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.1, 8.1.1
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Blocker
> Fix For: 8.1.2
>
> Attachments: SOLR-13583.patch
>
>
> SOLR-13262 changed the behavior of most collection admin commands so that they always resolve aliases by default. In most cases this is desireable behavior but it also prevents executing commands on the collections that have the same name as an existing alias (which usually points to a different collection).
> This behavior also breaks the REINDEXCOLLECTION command with {{removeSource=true,}} which can also lead to data loss.
> This issue can be resolved by adding either an opt-in or opt-out flag to the collection admin commands that specifies whether the command should attempt resolving the provided name as an alias first. From the point of view of ease of use this could be an opt-out option, from the point of view of data safety this could be an opt-in option.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org