[
https://issues.apache.org/jira/browse/SOLR-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319645#comment-16319645
]
Erick Erickson edited comment on SOLR-11218 at 1/10/18 3:54 AM:
----------------------------------------------------------------
Spoilsport ;).
Yeah, any test that relies on the old behavior to delete an alias out from
under an existing collection (no matter how that alias got made) is going to
fail. I'll raise a separate JIRA, should be an easy fix but may take a bit to
flush them all out.
Thanks!
was (Author: erickerickson):
Spoilsport ;).
Yeah, any test that relies on the old behavior to delete an alias out from
under an existing collection (no matter how that alias got made) is going to
I'll raise a separate JIRA, should be an easy fix.
Thanks!
> Fail and return an error when attempting to delete a collection that's part
> of an alias
> ---------------------------------------------------------------------------------------
>
> 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
> Fix For: 7.3
>
> Attachments: SOLR-11218.patch, SOLR-11218.patch, SOLR-11218.patch,
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
