Filtered traverse in LTEQ direction appears not to work

Bug #1046049 reported by John M Bradley
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Akiban Persistit
Fix Released
Medium
Peter Beaman

Bug Description

If a key filter is set up to specify a key in the range of BEFORE -> searchValue, and a LTEQ traverse from AFTER is performed, the traverse fails to find any key.

The complementary traverse in the forward direction, i.e., filter searchValue -> AFTER and a GTEQ traverse from BEFORE, seems to work, hence this report.

Attached is a program to exhibit the observed behavior. If I'm misunderstanding something here, I apologize in advance.

Related branches

Revision history for this message
John M Bradley (j5b) wrote :
Peter Beaman (pbeaman)
Changed in akiban-persistit:
importance: Undecided → Medium
status: New → Fix Committed
milestone: none → 3.2.0
assignee: nobody → Peter Beaman (pbeaman)
Changed in akiban-persistit:
milestone: 3.2.0 → 3.2.1
Changed in akiban-persistit:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.