[ https://issues.apache.org/jira/browse/SOLR-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Høydahl closed SOLR-3714. ----------------------------- Resolution: Not A Bug Closing as not a bug since we document that unique ID must not be analyzed. In the schema file itself, it is clearly stated that *"Do NOT change the type and apply index-time analysis to the <uniqueKey> as it will likely make routing in SolrCloud and document replacement in general fail."* > SolrCloud fails to query documents if the primary key field is of type > "lowercase" > ---------------------------------------------------------------------------------- > > Key: SOLR-3714 > URL: https://issues.apache.org/jira/browse/SOLR-3714 > Project: Solr > Issue Type: Bug > Components: SolrCloud > Affects Versions: 4.0-ALPHA > Reporter: Daniel Collins > > Running the default SolrCloud tutorial, if you change the id field to type > "lowercase" instead of "string", and re-run the tests (indexing all the > documents in exampledocs), queries find strange results.. > Querying for *:* and rows=10 returns numFound as 26 docs, setting rows = 20 > returns 23 docs, and setting rows=50, returns 12 docs! > Querying for specific ids seems hit and miss as well, the purely lowercase > ids "?q=id:belkin" work ok, but anything with uppercase or mixed case ids > fails to be found. > The index is clearly correct as booting the serer without zookeeper (just > removing -DzkRun from the command line) returns all the expected docs, but > somehow zookeeper is interfering with the queries? -- 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