[
https://issues.apache.org/jira/browse/SOLR-11654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-11654.
---------------------------------
Resolution: Fixed
Fix Version/s: 7.5
Thanks; I'm glad that was simple. I added some \@Slow and \@Nightly
annotations here.
Beasted, ran all tests, and finally committed:
[https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=bc9ac994a4d738faec00f42b1cd3585bd2570c65]
I put you as the "Author" in git – something we don't really have a
policy/practice for/against but I figure it makes sense to do this for
contributors.
> TimePartitionedUpdateProcessor.lookupShardLeaderOfCollection should route to
> the ideal shard
> --------------------------------------------------------------------------------------------
>
> Key: SOLR-11654
> URL: https://issues.apache.org/jira/browse/SOLR-11654
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Fix For: 7.5
>
> Attachments: SOLR-11654.patch, SOLR-11654.patch, SOLR-11654.patch,
> SOLR-11654.patch, SOLR-11654.patch
>
>
> {{TimePartitionedUpdateProcessor.lookupShardLeaderOfCollection}} looks up the
> Shard/Slice to talk to for the given collection. It currently picks the
> first active Shard/Slice but it has a TODO to route to the ideal one based on
> the router configuration of the target collection. There is similar code in
> CloudSolrClient & DistributedUpdateProcessor that should probably be
> refactored/standardized so that we don't have to repeat this logic.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
