[
https://issues.apache.org/jira/browse/SOLR-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304981#comment-16304981
]
Erick Erickson commented on SOLR-11218:
---------------------------------------
As you can probably tell, I'm clearing out some backlog over the holidays.....
I think the right thing is to fail to delete a collection if there's an alias
pointing to it. In large, complex installations the "fail early" principle
holds I think.
The alternative is to fail silently. By that I mean we have an alias pointing
to a collection that doesn't exist. If we just ignore the collection that
doesn't exist then it'll be hard to track down.
I'll work up a patch for same, but won't commit until after people come back
from the holidays and have a chance to comment.
> Beef up alias testing when an alias and collection have the same name
> ---------------------------------------------------------------------
>
> Key: SOLR-11218
> URL: https://issues.apache.org/jira/browse/SOLR-11218
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Attachments: SOLR-11218.patch
>
>
> We don't really have good tests that when an alias and collection have the
> same name "the right thing" happens. In this case, admin operations should
> operate on the collection rather than the alias.
> Additionally we should have some tests to insure that alias resolution takes
> precedence for adds and searches in this case.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
