[
https://issues.apache.org/jira/browse/SOLR-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya updated SOLR-10011:
----------------------------------------
Attachment: SOLR-10011.patch
Here's a patch that introduces a new abstract method, getPointRangeQuery(). The
getRangeQuery() method either delegates to this getPointRangeQuery method, i.e.
in case of indexed=true or docValues=false, or delegates to another method for
create a DocValuesRangeQuery. Modified the tests to check for the correctness
of such fields.
FWIW, this was necessary while working on SOLR-5944, since for fields where
indexed=false, stored=false, docValues=true, the updates can do in-place
modification to the docValues, but current code would've ignored the docValues
altogether and performed queries on the points field.
[~tomasflobbe], can you please review?
> Non-indexed PointFields with DVs should use DocValuesRangeQuery
> ---------------------------------------------------------------
>
> Key: SOLR-10011
> URL: https://issues.apache.org/jira/browse/SOLR-10011
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Attachments: SOLR-10011.patch
>
>
> PointFields with indexed=false, docValues=true seem to be using
> (Int|Double|Float|Long)Point.newRangeQuery() for performing exact matches and
> range queries. However, they should instead be using DocValuesRangeQuery.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
