-
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
[ML-DataFrame] Dataframe REST cleanups #39451
Conversation
Pinging @elastic/ml-core |
assertEquals("body_id", dataFrameTransformConfig.getId()); | ||
|
||
expectThrows(IllegalArgumentException.class, | ||
() -> createDataFrameTransformConfigFromString(pivotTransform, "other_id")); |
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.
You could also assert that the error message is as expected here. (For example this will detect if the body ID and URL ID are the wrong way around when the error message is formed.)
import java.io.IOException; | ||
import java.util.Map; | ||
|
||
public class DataFrameGetAndGetStatsIT extends DataFrameRestTestCase { |
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.
nit: All these tests seem like they could just be yml tests.
bedf97f
to
a1ab5c9
Compare
opened: #39497 (fails locally for a master build without this PR, therefore unrelated) |
run elasticsearch-ci/1 |
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
fix a couple of odd behaviors of data frame transforms REST API's: - check if id from body and id from URL match if both are specified - do not allow a body for delete - allow get and stats without specifying an id
fix a couple of odd behaviors of data frame transforms REST API's: