[
https://issues.apache.org/jira/browse/LUCENE-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628728#comment-13628728
]
Akos Kitta commented on LUCENE-4824:
------------------------------------
Despite of several bug fixes in the join module for the 4.2. release, I still
have different results for the same query time joining when the fields are
stored as string and long.
I've already looked into the issue but stuck at
{noformat}
org.apache.lucene.search.MultiTermQueryWrapperFilter.getDocIdSet(AtomicReaderContext,
Bits){noformat}
I've noticed that an irrelevant document ID is collected with the
{noformat}org.apache.lucene.search.join.TermsQuery.SeekingTermSetTermsEnum{noformat}
to the bitset.
I'm quite eager to contribute some kind of solution if someone could give me
some advice or pointer.
Thanks is advance!
> Query time join returns different results based on the field type
> -----------------------------------------------------------------
>
> Key: LUCENE-4824
> URL: https://issues.apache.org/jira/browse/LUCENE-4824
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/join
> Affects Versions: 4.1
> Reporter: Akos Kitta
> Labels: newbie
> Attachments: QueryTimeJoinTest.java
>
>
> I'm experiencing different query time joining behavior based on the type of
> the 'toField' and 'fromField'. Basically I got correct results when both
> 'toField' and 'fromField' are StringField, but incorrect in case of LongField.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
