lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5092) join: don't expect all filters to be FixedBitSet instances
Date Thu, 04 Jul 2013 15:55:49 GMT


Uwe Schindler commented on LUCENE-5092:

In general I am not happy with the backwards iteration at all. I have the feeling that this
is a "bug" of block join. In my opinion the order of child / parent documents should be reversed,
so the search for the parent (or child dont know) could go forward only.

This would make existing indexes incompatible (if child/parent documents are reversed), but
we could add a IndexSorter based reorder machanism.

[~mikemccand]: Any inside knowledge about this?
> join: don't expect all filters to be FixedBitSet instances
> ----------------------------------------------------------
>                 Key: LUCENE-5092
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/join
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>            Priority: Minor
> The join module throws exceptions when the parents filter isn't a FixedBitSet. The reason
is that the join module relies on prevSetBit to find the first child document given a parent
> As suggested by Uwe and Paul Elschot on LUCENE-5081, we could fix it by exposing methods
in the iterators to iterate backwards. When the join modules gets an iterator which isn't
able to iterate backwards, it would just need to dump its content into another DocIdSet that
supports backward iteration, FixedBitSet for example.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message