[
https://issues.apache.org/jira/browse/SOLR-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120470#comment-16120470
]
Erick Erickson commented on SOLR-11218:
---
It's common to recommend when people need to re-index for any reason that they:
1> create a new collection
2> index the corpus to the new collection and verify it
3> create an alias pointing to the new collection as their original collection
4> delete the old collection.
They may or may not have an alias already pointing to the old collection that's
being replaced.
If they don't already have an alias, this leaves them with:
> a collection named old_collection
> a collection named new_collection
> an alias old_collection->new_collection
What happens when the delete old_collection now?
Current behavior is that delete "does the right thing" and deletes
old_collection rather than new_collection,
but if this behavior changes it could be disastrous for users so this test
insures that this behavior.
I have a test patch in progress I'll commit today if it works.
> Add a test that insures that you can delete the underlying collection if you
> have an alias of the same name pointing to a different collection
> --
>
> 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
>
--
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
