You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2020/01/03 20:49:00 UTC
[jira] [Created] (SOLR-14164) Replace Solr's FunctionRangeQuery
with Lucene's
David Smiley created SOLR-14164:
-----------------------------------
Summary: Replace Solr's FunctionRangeQuery with Lucene's
Key: SOLR-14164
URL: https://issues.apache.org/jira/browse/SOLR-14164
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: David Smiley
Assignee: David Smiley
Solr has a FunctionRangeQuery. It is constant scoring and also a post-filter. Lucene has a FunctionRangeQuery that I added years ago LUCENE-6919. It is not constant scoring as it scores based on the wrapped ValueSource, although this is easily made the same as Solr's by wrapping in a ConstantScoreQuery. And it uses Lucene's TwoPhaseIterator indirectly which is equivalent functionality to Solr's PostFilter. Consequently we can remove Solr's implementation. Additionally, ValueSourceRangeFilter is a piece of the puzzle that can be removed as Solr's FunctionQuery was a wrapper around this specifically. FYI Once upon a time, Query and Filter were separate, then Filter was made to subclass Query and then Filter was relegated to Solr as tech debt.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org