[
https://issues.apache.org/jira/browse/SOLR-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234860#comment-14234860
]
Erik Hatcher edited comment on SOLR-6822 at 12/5/14 12:56 AM:
--------------------------------------------------------------
But if id is string and _ root _ is int, the actual bytes indexed will be
different, and thus the printable/string version is needed for the TermQuery.
No? Granted, we shouldn't allow for that, and there is a comment to that
effect in there as well {{sdoc.setField("_root_", idField); // should this
be a string or the same type as the ID?}} - maybe we can make this a schema
initialization error if those two fields don't match type like they should?
was (Author: ehatcher):
But if id is string and {{_root_}} is int, the actual bytes indexed will be
different, and thus the printable/string version is needed for the TermQuery.
No? Granted, we shouldn't allow for that, and there is a comment to that
effect in there as well {{sdoc.setField("_root_", idField); // should this
be a string or the same type as the ID?}} - maybe we can make this a schema
initialization error if those two fields don't match type like they should?
> Block Join duplicates when _root_ is different type than uniqueKey
> ------------------------------------------------------------------
>
> Key: SOLR-6822
> URL: https://issues.apache.org/jira/browse/SOLR-6822
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.10
> Reporter: Greg Harris
>
> If you have in your setup {{_root_}} a different type than your uniqueKey,
> when you update blocks with the same id, you start getting duplicates of the
> entire block. So if you have parent->child->grandchild and update the block
> with the same or different children you will have both blocks in their
> entirety still in the index found with "star":"star"
> This can further create weirdness when doing calls from different shards as a
> call to the shard itself will give back all results... a call to a different
> shard with shards=dupeshard will take out the duplicates being sent for
> rows=x and affects the numFound and total docs returned if there are dupes in
> the rows being returned. So it is not consistent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
