Floating point keys, lower-bound queries, cursors

[enomado]

Hello. First of all thank for all stuff you creating. I dont know my questions suitable for its design, but I ask:

I'm parquet/arrow guy, and my queries is mostly things like lower-bound on floating point columns. So my questins are:

1. Floating point keys. Ord of bytes of float is almost the same as float itself, there king of difference in neg, NaN, INF.
2. Lower/upper-bound queries. I know there is range-queries, But I dont know, is is cheap to do semi-undounded range queries to get next item?
3. Cursors. I want something like - "next key from current". Or may be real cursors, or internal ids exposed.

[marvin-j97]

1. Keys need to be lexicographical. If you can encode floating point numbers that way, you should be able to create queries over them.

2. A semi-open range has the same cost as a closed range when only .next() is used.

3. There are no internal IDs really - the key is the defining factor for ordering - if you want the item after prev you can do .range((Excluded(prev), Unbounded)).next()