Details
Description
ForestDB iterator created with start key:
0x73, 0x37, 0x35, 0x34, 0x36, 0x32, 0x34, 0xff
with options:
FDB_ITR_NO_DELETES | FDB_ITR_SKIP_MAX_KEY
does not see the key:
0x73, 0x37, 0x35, 0x34, 0x36, 0x32, 0x34, 0xff, 0x00, 0x00, 0x00
Even though it should sort higher (when memcmp of common portion is 0, length is consulted).
I posted about there here:
https://groups.google.com/d/msg/forestdb/iwgOs0kV5-U/KEjVXAjaBAAJ
and Jung-Sang confirmed he saw the same behavior if WAL is manually flushed before iterator_init()
Attachments
Issue Links
- blocks
-
MB-18219 [FTS] Highlighting of results and snippet selection is wrong
- Closed
For Gerrit Dashboard: MB-18712 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
61505,4 | MB-18712 Fix to a bug on comparison between NULL and zero-filled chunk | master | forestdb | Status: MERGED | +2 | +1 |
61554,2 | [BP] MB-18712 Fix to a bug on comparison between NULL and zero-filled chunk | stable | forestdb | Status: MERGED | +2 | +1 |