Skip to content

feat: add client-side rollover for Elasticsearch Serverless#390

Closed
siddharthlatest wants to merge 4 commits into
devfrom
dev-9.3.0
Closed

feat: add client-side rollover for Elasticsearch Serverless#390
siddharthlatest wants to merge 4 commits into
devfrom
dev-9.3.0

Conversation

@siddharthlatest

Copy link
Copy Markdown
Member

Serverless rejects rollover conditions in the API body, so evaluate max_age/max_docs/max_size client-side and call rollover without conditions. Keeps the existing @midnight/@hourly cron and post-rollover index cleanup unchanged.

siddharthlatest and others added 4 commits June 11, 2026 22:31
…ey auth

Detect serverless clusters via build_flavor and remap dot-prefixed meta
indices to rs_* names, since Serverless rejects user-created hidden indices.
Add ES_API_KEY upstream auth, strip unsupported index settings on create,
and use _cat/indices for index size where _stats is unavailable.

Co-authored-by: Cursor <cursoragent@cursor.com>
Drop confidential rs-api-server clone and package only build/ artifacts.

Co-authored-by: Cursor <cursoragent@cursor.com>
Serverless rejects rollover conditions in the API body, so evaluate
max_age/max_docs/max_size client-side and call rollover without
conditions. Keeps the existing @midnight/@hourly cron and post-rollover
index cleanup unchanged.
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