[
https://issues.apache.org/jira/browse/SOLR-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403246#comment-17403246
]
Andrzej Bialecki edited comment on SOLR-12628 at 8/23/21, 3:38 PM:
-------------------------------------------------------------------
Correct. However ... after dealing with {{SplitShardCmd}} and its convoluted
logic and error handling - I think the merge Cmd would introduce a similar
level of complexity and fragility. So yeah, the routing logic could remain the
same but the command itself would still be complex to write / test / debug &
harden so that it's useful in production.
was (Author: ab):
Correct. However ... after dealing with {{SplitShardCmd}} and it's convoluted
logic and error handling - I think the merge Cmd would introduce a similar
level of complexity and fragility. So yeah, the routing logic could remain the
same but the command itself would still be complex to write / test / debug &
harden so that it's useful in production.
> Support multiple ranges in a slice
> ----------------------------------
>
> Key: SOLR-12628
> URL: https://issues.apache.org/jira/browse/SOLR-12628
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
>
> Currently {{Slice}} supports only a single {{Range}}. In order to effectively
> merge shards with non-adjacent ranges we need to support multiple ranges per
> slice.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
