[jira] [Updated] (SOLR-7272) Use OverseerCollectionProcessor.ROUTER and DocCollection.DOC_ROUTER consistently

["Gregory Chanan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Chanan updated SOLR-7272:
---------------------------------
    Attachment: SOLR-7272.patch

Trivial patch -- you'll notice we are now using DOC_ROUTER in a couple places where the cluster state is being read from ZK.

> Use OverseerCollectionProcessor.ROUTER and DocCollection.DOC_ROUTER consistently
> --------------------------------------------------------------------------------
>
>                 Key: SOLR-7272
>                 URL: https://issues.apache.org/jira/browse/SOLR-7272
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>         Attachments: SOLR-7272.patch
>
>
> This is something I noticed while working on SOLR-7271.  There are two different router constants:
> #1. OverseerCollectionProcessor.ROUTER: represents the argument(s) to the OverseerCollectionProcessor
> #2 DocCollection.DOC_ROUTER: represents the router information as stored in the clusterstate in ZK
> But these are sometimes used in the other contexts, which can cause issues if the constant values are not the same (as in SOLR-7271).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org