[ https://issues.apache.org/jira/browse/SOLR-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar updated SOLR-4797: ---------------------------------------- Attachment: SOLR-4797.patch Changes: # Partition the range with the correct router # Index docs with composite ids > Sub shards have wrong hash range in cluster state except when using > PlainIdRouter > --------------------------------------------------------------------------------- > > Key: SOLR-4797 > URL: https://issues.apache.org/jira/browse/SOLR-4797 > Project: Solr > Issue Type: Bug > Components: SolrCloud > Affects Versions: 4.3 > Reporter: Shalin Shekhar Mangar > Assignee: Shalin Shekhar Mangar > Fix For: 4.4 > > Attachments: SOLR-4797.patch > > > The overseer collection processor always uses PlainIdRouter to partition the > hash range. However, some router implementations (most notably > CompositeIdRouter) can provide a different implementation to partition hash > ranges. So there can be a mismatch between the hash ranges which are > persisted in clusterstate.xml for sub shards and the actual index which is > split using the collection's configured router impl. > This bug does not affect collections using PlainIdRouter. > The overseer collection processor should always use the collection's > configured router to partition ranges. -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org