[
https://issues.apache.org/jira/browse/LUCENE-8870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873009#comment-16873009
]
Adrien Grand commented on LUCENE-8870:
--------------------------------------
bq. Currently NumericDocValuesField does not support the option for stored. So
users need to add a separate StoredField.
I'm viewing this one as a feature. :) Having the same field indexed and stored
often makes sense because the analyzer takes care of converting the text into
the internal representation that the index cares about. But for doc values, we
expect users to do this work of converting the data to what works for Lucene.
For instance if you are indexing doubles, you would likely index as a byte[] in
points, use the long bits of the double in doc values, and use the double
directly for storing, these are 3 different representations for the same data.
My gut feeling is that trying to fold everything into a single field would make
things more complicated rather than simpler.
> Support numeric value in Field class
> ------------------------------------
>
> Key: LUCENE-8870
> URL: https://issues.apache.org/jira/browse/LUCENE-8870
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Namgyu Kim
> Priority: Major
> Attachments: LUCENE-8870.patch
>
>
> I checked the following comment in Field class.
> {code:java}
> // TODO: allow direct construction of int, long, float, double value too..?
> {code}
> We already have some fields like IntPoint and StoredField, but I think it's
> okay.
> The test cases are set in the TestField class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
