-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some progress on failing runtime fields tests #61098
Some progress on failing runtime fields tests #61098
Conversation
This breaks apart the a test for the `terms` aggregation into one that work for runtime fields and one that doesn't.
Pinging @elastic/es-search (:Search/Search) |
|
||
- do: | ||
indices.refresh: {} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see only one test added here, so I don't follow what is being split. Also, would it make sense to make the test changes to master directly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm cutting this test in half.
I think it'd make sense to do this in master if we expected folks to hack on these tests before we merge this down. I'm mostly the person who I'd expect to hack on these tests so I don't think that is super likely.
Thanks @javanna ! |
… master) This breaks apart the a test for the `terms` aggregation into one that work for runtime fields and one that doesn't.
#61101) This breaks apart the a test for the `terms` aggregation into one that work for runtime fields and one that doesn't.
… 7.x) This breaks apart the a test for the `terms` aggregation into one that work for runtime fields and one that doesn't.
This breaks apart the a test for the
terms
aggregation into one thatwork for runtime fields and one that doesn't.