[
https://issues.apache.org/jira/browse/SOLR-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015934#comment-17015934
]
ASF subversion and git services commented on SOLR-13892:
--------------------------------------------------------
Commit 097990ba9cd87b6906ada59bee64782c4cc21066 in lucene-solr's branch
refs/heads/jira/SOLR-13892 from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=097990b ]
SOLR-13892: Add TPI implementation for benchmarking
In some benchmarking it looks like the TPI implementation has the same
perf benefits as the postfilter implementation, which was mostly
expected. The current implementation is very rough (lots of duplication
and debug logging), but I'm sharing it to give context to performance
results I'm posting at the same time.
> Add postfilter support to {!join} queries
> -----------------------------------------
>
> Key: SOLR-13892
> URL: https://issues.apache.org/jira/browse/SOLR-13892
> 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-13892.patch, SOLR-13892.patch,
> join-increasing-from-matches1.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The JoinQParserPlugin would be a lot performant in many use-cases if it could
> operate as a post-filter, especially when doc-values for the involved fields
> are available.
> With this issue, I'd like to propose a post-filter implementation for the
> {{join}} qparser.
--
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
