[
https://issues.apache.org/jira/browse/SOLR-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016075#comment-17016075
]
David Smiley commented on SOLR-13892:
-------------------------------------
RE branches and "commit spamming", I think you will still have a problem
because you started your branch with "jira/". To avoid the spamming, the
branch needs to start with either "lucene" or "solr", lowercase. Also consider
pushing to your fork, which avoids this issue entirely. Any way, I wouldn't
redo a PR over this matter.
> 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-matches-tpi.png, join-increasing-from-matches1.png
>
> Time Spent: 1h
> 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
