[
https://issues.apache.org/jira/browse/SOLR-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930482#comment-15930482
]
Tomás Fernández Löbbe commented on SOLR-10237:
----------------------------------------------
Results will be incorrect if {{IndexOrDocValuesQuery}} decides to use the
DocValues query. In my tests it would always return incorrect results because
the DV query was always chosen (because there were no values in the DV field).
The "sometimes" would happen in odd situations I guess, if someone has a field
that has some documents with DV and some without (e.g. if we fix this in 6.6
and someone has an index built with 6.5 using point fields and upgrades without
re-indexing).
> Poly-Fields should work with subfield that have docValues=true
> --------------------------------------------------------------
>
> Key: SOLR-10237
> URL: https://issues.apache.org/jira/browse/SOLR-10237
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Tomás Fernández Löbbe
> Attachments: SOLR-10237.patch, SOLR-10237.patch, SOLR-10237.patch
>
>
> DocValues aren’t really supported in poly-fields at this point, but they
> don’t complain if the schema definition of the subfield has docValues=true.
> This leaves the index in an inconsistent state, since the SchemaField has
> docValues=true but there are no DV for the field.
> Since this breaks compatibility, I think we should just emit a warning unless
> the subfield is an instance of {{PointField}}. With
> {{\[Int/Long/Float/Double/Date\]PointField}} subfields, this is particularly
> important, since they use {{IndexOrDocValuesQuery}}, that would return
> incorrect results.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
