[
https://issues.apache.org/jira/browse/LUCENE-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lu Xugang updated LUCENE-10162:
-------------------------------
Attachment: LUCENE-10162-1.patch
> Add IntField, LongField, FloatField and DoubleField classes to index both
> points and doc values
> -----------------------------------------------------------------------------------------------
>
> Key: LUCENE-10162
> URL: https://issues.apache.org/jira/browse/LUCENE-10162
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-10162-1.patch
>
>
> Currently we have IntPoint, LongPoint, FloatPoint and DoublePoint on the one
> hand, and NumericDocValuesField and SortedNumericDocValuesField on the other
> hand.
> When we introduced these classes, this distinction made sense: use the
> XXXPoint classes if you want your numeric fields to be searchable and the
> XXXDocValuesField classes if you want your numeric fields to be
> sortable/aggregatable.
> However since then, we introduced logic to take advantage of doc values for
> filtering (IndexOrDocValuesQuery) and enhanced sorting to take advantage of
> the Points index to skip non-competitive documents. So even if you only need
> searching, or if you only need sorting, it's likely a good idea to index both
> with points *and* doc values.
> Could we make this easier on users by having XXXField classes that
> automatically do it as opposed to requiring users to add both an XXXPoint and
> an XXXDocValuesField for every numeric field to their index? This could also
> make consuming these fields easier, e.g. factory methods for range queries
> could automatically use IndexOrDocValuesQuery.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
