[
https://issues.apache.org/jira/browse/SOLR-13890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009789#comment-17009789
]
Mikhail Khludnev commented on SOLR-13890:
-----------------------------------------
bq. Backwards compatible? Does that apply here
Fair. It's private. Haven't noticed it before.
bq. avoid per-segment iteration for performance reasons.
Here in _per-segment iteration_ you mean _reading per-segment ordinals_, since
iteration, scorer, TPI are always per-segment. The patch avoids _reading
per-segment ordinals_ via top-level wrapper SlowAtomicReader, which is a little
bit outdated concept. What code can do: obtain per-segment docvalues, get
segement ordinal per doc, than map it to global ordinal (that's done in
MultiDocValues), than global ordinal might be checked in bitset (if I remember
concept right) .
Then, cast occurrence in file doesn't mean a query doesn't have a condition to
accept Lucene's searcher. As a test case you can use this query in
deleteByQuery.
> 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, 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: 1h 20m
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
