[
https://issues.apache.org/jira/browse/LUCENE-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185714#comment-13185714
]
Michael McCandless commented on LUCENE-3602:
--------------------------------------------
Oh yeah MTQ already defaults to that rewrite method :)
Really, since you know the exact number of terms up front... you could
specialize it to constant BQ or filter yourself... but that can be later.
I don't think you should be calling TreeSet.higher on every term check --
that's a relatively costly binary search through the TreeSet each time. Really
you should be able to just walk through (with your own upto++) the pre-sorted
BytesRef[] you pulled from the BytesRefHash. Then we should retest seek vs
next...
> Add join query to Lucene
> ------------------------
>
> Key: LUCENE-3602
> URL: https://issues.apache.org/jira/browse/LUCENE-3602
> Project: Lucene - Java
> Issue Type: New Feature
> Components: modules/join
> Reporter: Martijn van Groningen
> Fix For: 3.6, 4.0
>
> Attachments: LUCENE-3602.patch, LUCENE-3602.patch, LUCENE-3602.patch,
> LUCENE-3602.patch
>
>
> Solr has (psuedo) join query for a while now. I think this should also be
> available in Lucene.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
