opensearch-project/OpenSearch

[Star Tree] Removal of @ExperimentalApi annotations in star-tree related code files

Open

#18,499 opened on Jun 11, 2025

View on GitHub
 (9 comments) (1 reaction) (3 assignees)Java (8,123 stars) (1,505 forks)batch import
IndexingSearchenhancementgood first issue

Description

Is your feature request related to a problem? Please describe

Follow-up on https://github.com/opensearch-project/OpenSearch/pull/18070

Describe the solution you'd like

Since the star-tree is not feature-flagged as experimental anymore, we need to remove up @ExperimentalApi annotations across code-files across indexing and search.

Related component

No response

Describe alternatives you've considered

No response

Additional context

Since this change does not involves considerable logical planning, I feel this is a low-effort good first issue as well, which involves minor code change, running spotless, and raising a PR.

Contributor guide

Tech stack
java
Domain
backendsearch
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaOpenSearch codebasefamiliarity with star tree
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Examine the referenced PR (https://github.com/opensearch project/OpenSearch/pull/18070) to understand which annotations were removed for other components. Then search for @ExperimentalApi annotations in star tree related files under the indexing and search directories. Use grep or IDE to find all occurrences. After removal, run spotless to format code, then compile and test to ensure no breakage. Consult issue comments for any additional context.