opensearch-project/query-insights

[FEATURE] Cache the cluster state request for query insights reader

Open

#351 opened on Jun 4, 2025

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)Java (34 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (27 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem?

Each time we invoke the reader, we make a request to the cluster state api to fetch all available indices. There are some overhead with this approach.

What solution would you like?

Ideally we should cache the index names and update the cache whenever the cluster state is changed

What alternatives have you considered?

A clear and concise description of any alternative solutions or features you've considered.

Do you have any additional context?

Add any other context or screenshots about the feature request here.

Contributor guide

Research direction
Look into the query insights reader implementation and locate the call to the cluster state API. Research how to cache the index names and invalidate the cache on cluster state changes. Examine existing test infrastructure to add coverage for the caching behavior.
Tech stack
java
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60