[ENH] Use binary search for gt/gte/lt/lte

[Sicheng-Pan]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • Updates the binary search algorithm for arrow block to match the latest std impl
  • The binary search now identifies the partition point instead of returning the value at the location
  • New utility function to scan a range of values for the same prefix
  • Now methods that yields a vector of records like get_by_prefix and get_gt returns Vec<(K, V)> instead of Option<Vec<&str, K, V>>. The empty vector is sufficient to indicate the absence of the specified (prefix, key)
• New functionality
  • With all the refactoring above, now get_gt/gte/lt/lte finds the starting point of the scan using binary search. Previously, we scan the entire block.

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

[Sicheng-Pan]

• [ENH] Use binary search for gt/gte/lt/lte #2894 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Sicheng-Pan and the rest of your teammates on Graphite

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[sanketkedia]

nit: The coupling of key=None and key=Some cases together in the same api seems forced to me

[Sicheng-Pan]

In our case None is equivalent to K::MIN, but we do not have a Min trait so an Option<K> is the best alternative I can think of.

[Sicheng-Pan]

Merge activity

• Oct 9, 3:59 PM EDT: A user started a stack merge that includes this pull request via Graphite.
• Oct 9, 3:59 PM EDT: A user merged this pull request with Graphite.