[
https://issues.apache.org/jira/browse/SOLR-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679494#comment-13679494
]
Yonik Seeley edited comment on SOLR-4221 at 6/10/13 1:33 PM:
-------------------------------------------------------------
Off the top of my head, some things left to do in this general area of "custom
sharding":
- ability to create a new shard via collections API (and other lifecycle
operations... delete, rename?)
-- probably want to have the option of either leaving it empty, or creating
new replicas
- anything that may make time based sharding easier
-- this probably includes shard aliasing, like we have collection aliasing now
- when creating a collection, the ability to specify a router (and associated
config for the router) and have that persisted, etc
- using request parameters or document fields to direct what shard an update is
for
-- I think a lot of this is done/working (implicit router), but lacks tests
Further down the road, we also need to consider what to do about deletes,
real-time get, or other operations where we would normally derive the shard
from the ID... if it's not provided in another form, then we could decide to
broadcast to all shards.
was (Author: [email protected]):
Off the top of my head, some things left to do in this general area of
"custom sharding":
- ability to create a new shard via collections API (and other lifecycle
operations... delete, rename?)
- probably want to have the option of either leaving it empty, or creating
new replicas
- anything that may make time based sharding easier
- this probably includes shard aliasing, like we have collection aliasing now
- when creating a collection, the ability to specify a router (and associated
config for the router) and have that persisted, etc
- using request parameters or document fields to direct what shard an update is
for
- I think a lot of this is done/working (implicit router), but lacks tests
Further down the road, we also need to consider what to do about deletes,
real-time get, or other operations where we would normally derive the shard
from the ID... if it's not provided in another form, then we could decide to
broadcast to all shards.
> Custom sharding
> ---------------
>
> Key: SOLR-4221
> URL: https://issues.apache.org/jira/browse/SOLR-4221
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
>
> Features to let users control everything about sharding/routing.
--
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]
