[ https://issues.apache.org/jira/browse/SOLR-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967743#comment-16967743 ]
Joel Bernstein commented on SOLR-13892: --------------------------------------- Just reviewing the join code. I always assumed that the slowness in the join was coming from: {code:java} public DocSet getDocSetEnumerate() throws IOException { {code} This does not seems to care about scoring, but I could be wrong. The only way to know for sure is to test so I'll load up an index and report back on the performance of \{!join} vs \{!join score=none} in the scenarios we were using. > 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