You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Jason Gerlowski (Jira)" <ji...@apache.org> on 2020/03/02 16:40:00 UTC

[jira] [Resolved] (SOLR-13890) Add postfilter support to {!terms} queries

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

Jason Gerlowski resolved SOLR-13890.
------------------------------------
    Fix Version/s: 8.5
                   master (9.0)
       Resolution: Fixed

> Add postfilter support to {!terms} queries
> ------------------------------------------
>
>                 Key: SOLR-13890
>                 URL: https://issues.apache.org/jira/browse/SOLR-13890
>             Project: Solr
>          Issue Type: Improvement
>          Components: query parsers
>    Affects Versions: master (9.0)
>            Reporter: Jason Gerlowski
>            Assignee: Jason Gerlowski
>            Priority: Major
>             Fix For: master (9.0), 8.5
>
>         Attachments: SOLR-13890.patch, SOLR-13890.patch, SOLR-13890.patch, SOLR-13890.patch, SOLR-13890.patch, SOLR-13890.patch, Screen Shot 2020-01-02 at 2.25.12 PM.png, post_optimize_performance.png, toplevel-tpi-perf-comparison.png
>
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> There are some use-cases where it'd be nice if the "terms" qparser created a query that could be run as a postfilter.  Particularly, when users are checking for hundreds or thousands of terms, a postfilter implementation can be more performant than the standard processing.
> WIth this issue, I'd like to propose a post-filter implementation for the {{docValuesTermsFilter}} "method".  Postfilter creation can use a SortedSetDocValues object to populate a DV bitset with the "terms" being checked for.  Each document run through the post-filter can look at their doc-values for the field in question and check them efficiently against the constructed bitset.



--
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