[
https://issues.apache.org/jira/browse/LUCENE-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184191#comment-13184191
]
Michael McCandless commented on LUCENE-3602:
--------------------------------------------
Looking great! I think we are getting close :)
Maybe use BytesRefHash (oal.util) to gather the terms and sort
them in the end? Then hold onto the BytesRef[] (sorted). It's
designed for exactly this usage...
Also, I think you should always seek in your FilteredTermsEnum, and
simply iterate yourself through the BytesRef[]? Probably perf wasn't
great before because you were calling TreeSet.higher on each term?
I think you should call setRewriteMethod in your TermSetQuery ctor, to
CONSTANT_SCORE_AUTO_REWRITE_DEFAULT, since we have no scores here.
This rewrite method uses BQ if number of terms/docs is "smallish" else
creates a filter, so it should give good perf.
> 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]
