[
https://issues.apache.org/jira/browse/SOLR-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595572#comment-13595572
]
Mark Miller commented on SOLR-4497:
-----------------------------------
Okay - committing the current state now.
bq. 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.
I think this is something we should consider. It actually came up before with
the clusterstate.json as well - I think we are actually okay with how that
works currently though, but it may make sense to have the overseer to
distribute this. Let's make a new JIRA issue and investigate it as a future
improvement.
> 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: [email protected]
For additional commands, e-mail: [email protected]
