Skip to content

proposal: TSDB Index Lookup Planning #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dimitarvdimitrov
Copy link

@dimitarvdimitrov dimitarvdimitrov commented Jul 15, 2025

This proposal introduces extension points for TSDB index lookups that allow different execution strategies to address the problem of inefficient index lookup usage.

Part of the action items are being addressed in prometheus/prometheus#16835

@dimitarvdimitrov dimitarvdimitrov force-pushed the dimitar/tsdb-index-lookup-planning branch from 1b1af22 to 54ee679 Compare July 15, 2025 18:47
This proposal introduces extension points for TSDB index lookups that
allow different execution strategies to address the problem of inefficient
index lookup usage.

Key features:
- Extension points via LookupPlanner and LookupPlan interfaces
- Simple rule-based implementation example (ScanEmptyMatchersLookupPlanner)
- Enables downstream projects like Mimir, Thanos, and Cortex to implement
  custom optimization approaches
- Builds on scan matchers foundation from PR #16835

The proposal focuses on providing interfaces rather than prescribing
specific optimization strategies, allowing flexibility for different
deployment scenarios and use cases.

Signed-off-by: Dimitar Dimitrov <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant