[
https://issues.apache.org/jira/browse/SOLR-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864452#comment-15864452
]
ASF subversion and git services commented on SOLR-10011:
--------------------------------------------------------
Commit c27880e332722e992294e05749b63300d3eaab44 in lucene-solr's branch
refs/heads/branch_6x from Tomas Fernandez Lobbe
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c27880e ]
SOLR-10011: Add NumberType getNumberType() to FieldType and deprecate
LegacyNumericType getNumericType()
Modify references to getNumericType() to use the new getNumberType().
NumberType is shared for the different numeric implementations supported in
Solr (TrieFields and PointFields).
CC SOLR-8396
> 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
> Assignee: Ishan Chattopadhyaya
> Attachments: SOLR-10011.patch, 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
