[jira] [Commented] (SOLR-4497) Collection Aliasing.

["Yonik Seeley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593918#comment-13593918 ] 

Yonik Seeley commented on SOLR-4497:
------------------------------------

We should also strive for 100% visibility of an alias once the call returns.
For example, one should be able to script a call to create an alias and then immediately use it w/o worrying about some nodes not seeing it yet.
The easiest way to implement this would be to re-read the aliases from ZK on any "miss".
                
> Collection Aliasing.
> --------------------
>
>                 Key: SOLR-4497
>                 URL: https://issues.apache.org/jira/browse/SOLR-4497
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.2, 5.0
>
>         Attachments: SOLR-4497.patch
>
>
> We should bring back the old aliasing feature, but for SolrCloud and with the ability to alias one collection to many.
> The old alias feature was of more limited use and had some problems, so we dropped it, but I think we can do this in a more useful way with SolrCloud, and at a level were it's not invasive to the CoreContainer.
> Initially, the search side will allowing mapping a single alias to multiple collections, but the index side will only support mapping a single alias to a single collection.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org