[
https://issues.apache.org/jira/browse/LUCENE-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-4251:
---------------------------------
Attachment: LUCENE-4251_FunctionRangeQuery.patch
This is a newly written FunctionRangeQuery that I propose be added to the
"query" module. It's mostly a wrapper around the method
FunctionValues.getRangeScorer (producing a ValueSourceScorer). Furthermore I
enhanced ValueSourceScorer to use the TwoPhaseIterator API. Obviously this
needs to be tested, which I haven't done yet. getRangeScorer isn't tested
either; it's only used by Solr, which I assume is tested but that's irrelevant
since it should be tested in Lucene. This patch adds lucene.internal to
ValueSourceScorer since I feel it's internal.
note: this is being done in part as it relates to LUCENE-6650 (remove
dependency of Filter from spatial module). PointVectorStrategy uses this.
> Port Solr's ValueSourceRangeFilter to Lucene query module
> ---------------------------------------------------------
>
> Key: LUCENE-4251
> URL: https://issues.apache.org/jira/browse/LUCENE-4251
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/other
> Reporter: David Smiley
> Priority: Minor
> Fix For: 4.9, Trunk
>
> Attachments: LUCENE-4251_FunctionRangeQuery.patch
>
>
> Lucene spatial has ValueSourceFilter and Solr has ValueSourceRangeFilter
> (that has some more features). And someone asked for this in LUCENE-3875
> too. It should be ported over to the Lucene query module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
