-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[Transform] randomize integration tests using runtime fields #66148
[Transform] randomize integration tests using runtime fields #66148
Conversation
Pinging @elastic/ml-core (:ml/Transform) |
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.
LGTM
.endObject(); | ||
|
||
// random overlay of existing field |
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.
👍
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.
LGTM
I've left one comment.
new GroupConfig.Builder().groupBy("event", new TermsGroupSource.Builder().setField("event").setMissingBucket(missing).build()) | ||
.build() | ||
new GroupConfig.Builder().groupBy( | ||
"event", |
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.
Shouldn't this be termsField
?
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.
no, this is the output field name, on the next line there is setField(termsField)
Having that said, it would be more understandable if input and output use different names
this change adds coverage for runtime fields to the continuous transform integration test cases. runtime fields are configured at random.
this change adds coverage for runtime fields to the continuous transform integration test cases. runtime fields are configured at random.
Note: I haven't changed integration tests for latest, because of the ongoing fields API rewrite.