I’m trying to list keys in a range, with a given limit and either using the original or reversed order.
Looking at the fdb traces, the original listing will mark for ReadConflict only the range that was consumed by the client (start → limit). But when I use the reverse getRange, the entire range is marked for ReadConflict (end → start), ignoring the limit indicator.
I’m creating a message here first to get a feedback on my testing approach, to be sure the problem is worth creating an issue on the github repository.
My source used for tests & with logs : FDB Reverse read conflicting ranges · GitHub (Testing using fdb & bindings in versions 7.1.21 & 6.3.23 / apiversion 710 & 630).
I’m creating keys [32, 33, 34, … 62, 63], then listing from [42 → 51), with a limit of 5. The normal order locks [42 → 46], but the reversed order will lock [42 → 51).
Thanks you for having a look