Skip to content

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

@bwplotka
Copy link
Member

bwplotka commented Sep 9, 2025

Do you mind a quick rebase? We just fixed CI (it guides users on some required formatting e.g. your file name should follow 0056-xyz.md)

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 <dimitar.dimitrov@grafana.com>
@dimitarvdimitrov dimitarvdimitrov force-pushed the dimitar/tsdb-index-lookup-planning branch from e69b121 to bdec687 Compare September 10, 2025 07:53
Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants