lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Vaillancourt (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-4497) Collection Aliasing.
Date Thu, 07 Mar 2013 04:22:15 GMT

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

Tim Vaillancourt edited comment on SOLR-4497 at 3/7/13 4:20 AM:
----------------------------------------------------------------

I think that is a good start. The change wouldn't be 100% immediate on return of the call,
but designing the client/app to expect this could be ok. If there was a STATUS call on the
Cores API that could detail the node's running alias, one could write an external script to
"check" that the change made it everywhere.

This lead me to wondering (again without understanding implications and design goals) would
it be best to have the Overseer push the change to all nodes (and write to ZK) vs relying
only on the change in ZK, which has delays.
                
      was (Author: tvaillancourt):
    I think that is a good start. The change wouldn't be 100% immediate on return of the call,
but designing the client/app to expect this could be ok. If there was a STATUS call on the
Cores API that could detail the node's running alias, one could write an external script to
"check" that the change made it everywhere.

This lead me to wondering (again without understanding implications and design goals) would
it be best to have the Overseer push the change to all nodes vs write to ZK?
                  
> 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: CDH-4497.patch, 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


Mime
View raw message