Dear Hibernate Search users/developers!

I've come across a strange behaviour when creating the resultset of a ChainedFilter. My first filter contains the docIDs [0, 5, 6, 10], the second filter only the docId 6. So the resulting DocIdSet that is created when chaining these 2 filters should have set the bit for docId 6 to true, right?
Other filter values seem to work correctly. For example, if the second filter contains docId 0 instead of 6, the resulting DocIdSet has set the bit for docId 0 to true. Similarly, if the second filter contains docIDs [1, 10] the bit for docId 10 is set.
So it seems to me that there's a bug in AndDocIdSet#makeDocIdSetOnAgreedBits() causing the result to be empty if there is only one docId in the second filter that is not the first entry in the first filter. I think the problem could be related to setting the votes to 0 after the initialization loop in makeDocIdSetOnAgreedBits() and thus losing the information that the second filter voted for docId 6. This is causing "++votes == iteratorSize" to be false and thus never set the result.
Could you confirm this? Maybe I didn't completely understand the algorithm... Any help (explanations, workarounds, bugfixes) would be greatly appreciated! I'm using version 3.3.0-Beta1 of hiberate search but the affected code in AndDocIdSet doesn't seem to have changed since the last final version.

best regards
christian

Could you create an issue in HSEARCH and preferably attach a test case. That would be much appreciated and would help us to verify and fix the problem.

--Hardy

Done. Please see http://opensource.atlassian.com/project ... SEARCH-610