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

Joel Bernstein edited comment on SOLR-13890 at 1/3/20 8:11 PM:
---------------------------------------------------------------

If we auto-default cache=false then I'm fine with moving forward with the top 
level docvalues / TPI approach. Let's just give the users a terms query thats 
fast and works well with a *large number of terms*, *larger indexes, large 
number of filters* in a *frequently indexing environment.* These goals cannot 
be achieved with the current filter cache. So let's turn it off by default for 
this implementation.

Then let's get a segment level filter cache in place.


was (Author: joel.bernstein):
If we auto-default cache=false then I'm fine with moving the top level 
docvalues / TPI approach. Let's just give the users a terms query thats fast 
and works well with a *large number of terms*, *larger indexes, large number of 
filters* in a *frequently indexing environment.* These goals cannot be achieved 
with the current filter cache. So let's turn it off by default for this 
implementation.

Then let's get a segment level filter cache in place.

> Add postfilter support to {!terms} queries
> ------------------------------------------
>
>                 Key: SOLR-13890
>                 URL: https://issues.apache.org/jira/browse/SOLR-13890
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: query parsers
>    Affects Versions: master (9.0)
>            Reporter: Jason Gerlowski
>            Assignee: Jason Gerlowski
>            Priority: Major
>         Attachments: 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
>
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to