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

ASF subversion and git services commented on SOLR-13309:
--------------------------------------------------------

Commit af8afee9aaa6d2fb40691f902bd1330e02763e0d in solr's branch 
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=af8afee9aaa ]

SOLR-13309: Introduce LongRangeField to expose Lucene 'LongRange' (#4192)

This commit adds a new field type, LongRangeField, that can be used to
hold singular or multi-dimensional (up to 4) ranges of longs.

LongRangeField is compatible with the previously added
`{!numericRange}` and supports similar syntax.

Co-authored-by: Claude Sonnet 4.6 <[email protected]>

> Add FieldTypes for Lucene IntRange, LongRange, FloatRange, DoubleRange
> ----------------------------------------------------------------------
>
>                 Key: SOLR-13309
>                 URL: https://issues.apache.org/jira/browse/SOLR-13309
>             Project: Solr
>          Issue Type: New Feature
>          Components: Schema and Analysis
>            Reporter: David Smiley
>            Assignee: Jason Gerlowski
>            Priority: Major
>              Labels: gsoc2019, mentor, pull-request-available
>             Fix For: 10.1
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> This issue is for adding Solr FieldType subclasses that expose the 
> functionality implemented by the Lucene classes: IntRange, LongRange, 
> FloatRange, DoubleRange.
> An attribute on the FieldType could specify the dimensionality 1-4.
> We'll need to come up with a syntax to specify the predicate: Intersects, 
> Contains, or Within.
> Credit to [~nknize] for implementing these cool classes at the Lucene level.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to