Search before asking
Description
Currently, BanyanDB's inverted index uses the byte index type to handle numeric data such as integers and floats. While this implementation works, it could be optimized for range queries, which are resource-intensive and critical for many use cases, like trace latency range queries. BanyanDB's underlying index now supports numeric index types designed explicitly for numeric data like integers and floats. This index type offers better performance for range-based operations.
This issue proposes replacing the byte index type with the numeric index type when indexing numeric data (int and float) to significantly improve range query performance.
Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?
Code of Conduct
Search before asking
Description
Currently, BanyanDB's inverted index uses the byte index type to handle numeric data such as integers and floats. While this implementation works, it could be optimized for range queries, which are resource-intensive and critical for many use cases, like trace latency range queries. BanyanDB's underlying index now supports numeric index types designed explicitly for numeric data like integers and floats. This index type offers better performance for range-based operations.
This issue proposes replacing the byte index type with the numeric index type when indexing numeric data (int and float) to significantly improve range query performance.
Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?
Code of Conduct