Skip to content

Deep terms agg#733

Merged
nik9000 merged 1 commit intomasterfrom
aggs_deep_terms
Jan 29, 2025
Merged

Deep terms agg#733
nik9000 merged 1 commit intomasterfrom
aggs_deep_terms

Conversation

@nik9000
Copy link
Member

@nik9000 nik9000 commented Jan 28, 2025

This adds a test for super deeply nested terms aggs

Copy link
Member

@gareth-ellis gareth-ellis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@nik9000 nik9000 merged commit 23f6712 into master Jan 29, 2025
26 checks passed
github-actions bot pushed a commit that referenced this pull request Jan 29, 2025
(cherry picked from commit 23f6712)
@github-actions
Copy link

💚 All backports created successfully

Status Branch Result
8.15

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

gareth-ellis pushed a commit that referenced this pull request Jan 30, 2025
(cherry picked from commit 23f6712)

Co-authored-by: Nik Everett <nik9000@gmail.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
@gareth-ellis gareth-ellis deleted the aggs_deep_terms branch August 18, 2025 16:00
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Dec 19, 2025
@esbenchmachine
Copy link
Collaborator

@nik9000
A backport is pending for this PR. Please add all required vX.Y version labels.

  • If it is intended for the current Elasticsearch release version, apply the corresponding version label.
  • If it also supports past released versions, add those labels too.
  • If it only targets a future version, wait until that version label exists and then add it.
    (Each rally-tracks version label is created during the feature freeze of a new Elasticsearch branch).

Backporting entails:

  1. Ensure the correct version labels exist in this PR.
  2. Ensure backport PRs have backport label and are passing tests.
  3. Merge backport PRs (you can approve yourself and enable auto-merge).
  4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport pending Awaiting backport to stable release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments