[
https://issues.apache.org/jira/browse/SOLR-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967757#comment-16967757
]
Mikhail Khludnev commented on SOLR-13892:
-----------------------------------------
{!join score=none} switches execution to
https://github.com/apache/lucene-solr/blob/4f16d87c7ee5d4cf6e335cfd464733b149d62eb5/lucene/join/src/java/org/apache/lucene/search/join/JoinUtil.java#L37
as a result of these, complexity of operation is proportional to number of
values under "from"-side of join. As you remind, classic {!join} complexity is
proportional of number of terms at "to"-side despite of "from"-side
selectivity.
> 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
> Priority: Major
> Attachments: SOLR-13892.patch
>
>
> 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
