[
https://issues.apache.org/jira/browse/SOLR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553117#comment-13553117
]
Dmitry Kan commented on SOLR-3755:
----------------------------------
"Somewhat related: control naming of shards. This could be applicable for both
hashing based collections and custom sharding based collections.
shardNames=myshard1,myshard2,myshard3?"
Would this suit to logical (e.g. date based) sharding as well? Do you plan to
support such a sharding type in the current shard splitting implementation? Not
sure, if this helps: we have implemented our own custom date based sharding
(splitting and routing) for solr 3.x and found it to be the most logical way of
sharding our data (both from the load balancing and use case point of view).
The routing implementation is done via loading a custom shards config file that
contains mapping of date ranges to shards.
> shard splitting
> ---------------
>
> Key: SOLR-3755
> URL: https://issues.apache.org/jira/browse/SOLR-3755
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Yonik Seeley
> Attachments: SOLR-3755.patch, SOLR-3755.patch
>
>
> We can currently easily add replicas to handle increases in query volume, but
> we should also add a way to add additional shards dynamically by splitting
> existing shards.
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
