I am starting work on adding 7.1 support to Tokio/Rust binding layer.
I was able to get a reasonable understanding of the Tentant APIs.
Regarding GetMappedRange, I was wondering if there was any documentation on how RecordLayer plans to make use of this feature?
Is there a branch/fork of RL that has already been adapted to use GetMappedRange?
@nblintao At the C API level, is there any difference between fdb_transaction_get_range and fdb_transaction_get_mapped_range other than the fact the former returns a stream of key-values, while the latter takes in a new parameter mapper, and returns a “mapped” key-value?
Would I be correct in assuming that there is no change in the behavior of the common parameters?
Yes there is no change in the behavior of the common parameters. I’ll release a detailed doc about GetMappedRange this week. I’ll keep you posted.
Thanks for the reply @nblintao! 
Based on your earlier pointers, I now have an implementation of Tokio/Rust bindings that supports get_mapped_range.
I am really excited about this feature. Given the fact that indexed lookup is the bread and butter of OLTP workloads, I can see how this feature can help in simplifying layer development and improving performance.
I am looking forward to your docs.
Are you also planning on introducing binding tester tests soon?
I just posted at Everything about GetMappedRange.
Based on your earlier pointers, I now have an implementation of Tokio/Rust bindings that supports get_mapped_range.
Great to hear!
Are you also planning on introducing binding tester tests soon?
I don’t have plan to add additional test for now.