[
https://issues.apache.org/jira/browse/SOLR-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817801#comment-16817801
]
David Smiley commented on SOLR-13262:
-------------------------------------
{quote}I'm also inclined to forbid sending updates to a non-routed alias that
consists of more than 1 collection - the current behavior is documented but
other than that it's unintuitive and misleading - a scenario where users would
want an update to succeed if they accidentally send it to a multi-collection
alias seems very unlikely? Of course, if it's there I'm sure someone uses and
relies on it, so there would be a back-compat aspect of this change...
{quote}
+1 to make this not supported anymore. It used to not be supported but I
changed it while working on routed aliases. In retrospect it should only work
as-such for routed aliases.
> Implement collection RENAME command
> -----------------------------------
>
> Key: SOLR-13262
> URL: https://issues.apache.org/jira/browse/SOLR-13262
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.0, master (9.0)
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Fix For: 8.1, master (9.0)
>
> Attachments: SOLR-13262.patch, SOLR-13262.patch, SOLR-13262.patch
>
>
> There's no RENAME collection command, which makes it unnecessarily difficult
> to manage long-term collection life-cycles.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
