[
https://issues.apache.org/jira/browse/SOLR-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833182#comment-15833182
]
ASF subversion and git services commented on SOLR-10011:
--------------------------------------------------------
Commit 285a1013ad04dd1cd5e5e41ffa93a87fe862c152 in lucene-solr's branch
refs/heads/master from [~ichattopadhyaya]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=285a101 ]
SOLR-10011: Refactor PointField & TrieField to now have a common base class,
NumericFieldType.
The TrieField.TrieTypes and PointField.PointTypes are now consolidated to
NumericFieldType.NumberType. This
refactoring also fixes a bug whereby PointFields were not using DocValues for
range queries for
indexed=false, docValues=true fields.
> Refactor PointField & TrieField to share common code
> ----------------------------------------------------
>
> Key: SOLR-10011
> URL: https://issues.apache.org/jira/browse/SOLR-10011
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Attachments: SOLR-10011.patch, SOLR-10011.patch, SOLR-10011.patch,
> SOLR-10011.patch
>
>
> We should eliminate PointTypes and TrieTypes enum to have a common enum for
> both. That would enable us to share a lot of code between the two field types.
> In the process, fix the bug:
> 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 DocValues based range
> query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
