[jira] [Commented] (SOLR-7272) Use OverseerCollectionProcessor.ROUTER and DocCollection.DOC_ROUTER consistently
[ https://issues.apache.org/jira/browse/SOLR-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387231#comment-14387231 ] ASF subversion and git services commented on SOLR-7272: --- Commit 1670178 from gcha...@apache.org in branch 'dev/trunk' [ https://svn.apache.org/r1670178 ] SOLR-7272: Use OverseerCollectionProcessor.ROUTER and DocCollection.DOC_ROUTER consistently 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7272) Use OverseerCollectionProcessor.ROUTER and DocCollection.DOC_ROUTER consistently
[ https://issues.apache.org/jira/browse/SOLR-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387233#comment-14387233 ] ASF subversion and git services commented on SOLR-7272: --- Commit 1670179 from gcha...@apache.org in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1670179 ] SOLR-7272: Use OverseerCollectionProcessor.ROUTER and DocCollection.DOC_ROUTER consistently 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org