[ 
https://issues.apache.org/jira/browse/LUCENE-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martijn van Groningen updated LUCENE-3602:
------------------------------------------

    Attachment: LUCENE-3602.patch

Attached a new patch!
* The static method now has Query as return type.
* TermsCollector and TermsQuery are package protected.
* TermsQuery now holds an int[] ords instead of an array of ByteRefs. This is a 
really nice improvement :)
* Swapped the const args of TermQuery. Consistency is important!
* After [some 
discussion|http://colabti.org/irclogger/irclogger_log/lucene-dev?date=2012-01-16#l231]
 moved the classes back to o.a.l.search.join package.  
* The query time joining uses the dict comparator on all places now (instead of 
ByteRef#UTF8AsUnicode).

In the that cmp==0 in TermsQuery at line 121; YES_AND_SEEK can't be returned. 
The FilteredTermsEnum prohibits seeking to a term smaller or equal then the 
current term. 
                
> 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, 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]

Reply via email to