refactor: replace RangeMap
with span-map
for better range lookup
#17006
+636
−848
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
refactor: replace
RangeMap
withspan-map
for better range lookupReplace custom
RangeMap
implementation withspan-map
crate for moreefficient range operations.
span-map
uses BTreeMap internally to storeranges, reducing boundary checks from O(n) to O(log n) when dealing
with overlapping ranges.
Also fixes single-key watch functionality that was previously broken.
Tests
Type of change
Related Issues
This change is