You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Kevin Risden (Jira)" <ji...@apache.org> on 2022/10/27 18:21:00 UTC

[jira] [Updated] (SOLR-14164) Replace Solr's FunctionRangeQuery with Lucene's

     [ https://issues.apache.org/jira/browse/SOLR-14164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Risden updated SOLR-14164:
--------------------------------
    Status: Patch Available  (was: Open)

> Replace Solr's FunctionRangeQuery with Lucene's
> -----------------------------------------------
>
>                 Key: SOLR-14164
>                 URL: https://issues.apache.org/jira/browse/SOLR-14164
>             Project: Solr
>          Issue Type: Sub-task
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> 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.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org