You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Atri Sharma (JIRA)" <ji...@apache.org> on 2019/05/14 16:51:00 UTC

[jira] [Commented] (LUCENE-8362) Add DocValue support for RangeFields

    [ https://issues.apache.org/jira/browse/LUCENE-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839614#comment-16839614 ] 

Atri Sharma commented on LUCENE-8362:
-------------------------------------

Attached is a patch for implementing this.

 

[^LUCENE-8362.patch]

> Add DocValue support for RangeFields 
> -------------------------------------
>
>                 Key: LUCENE-8362
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8362
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Nicholas Knize
>            Priority: Minor
>         Attachments: LUCENE-8362.patch
>
>
> I'm opening this issue to discuss adding DocValue support to {{\{Int|Long|Float|Double\}Range}} field types. Since existing numeric range fields already provide the methods for encoding ranges as a byte array I think this could be as simple as adding syntactic sugar to existing range fields that simply build an instance of {{BinaryDocValues}} using that same encoding. I'm envisioning something like {{doc.add(IntRange.newDocValuesField("intDV", 100)}} But I'd like to solicit other ideas or potential drawbacks to this approach.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org