Skip to content
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

Update Execute Watch to allow unknown fields #37498

Merged
merged 3 commits into from
Jan 18, 2019

Conversation

hub-cap
Copy link
Contributor

@hub-cap hub-cap commented Jan 15, 2019

ExecuteWatchResponse did not allow unknown fields. This commit fixes the
test and ConstructingObjectParser such that it does now allow unknown
fields. It also creates a new client side test for the response.

Relates #36938

ExecuteWatchResponse did not allow unknown fields. This commit fixes the
test and ConstructingObjectParser such that it does now allow unknown
fields. It also creates a new client side test for the response.

Relates elastic#36938
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

Copy link
Contributor

@jakelandis jakelandis left a comment

Choose a reason for hiding this comment

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

LGTM

@hub-cap
Copy link
Contributor Author

hub-cap commented Jan 16, 2019

@elasticmachine run gradle build tests 1
@elasticmachine run gradle build tests 2

@hub-cap
Copy link
Contributor Author

hub-cap commented Jan 17, 2019

@elasticmachine run gradle build tests 1

1 similar comment
@hub-cap
Copy link
Contributor Author

hub-cap commented Jan 18, 2019

@elasticmachine run gradle build tests 1

@hub-cap hub-cap merged commit 604422c into elastic:master Jan 18, 2019
hub-cap added a commit that referenced this pull request Jan 18, 2019
ExecuteWatchResponse did not allow unknown fields. This commit fixes the
test and ConstructingObjectParser such that it does now allow unknown
fields. It also creates a new client side test for the response.

Relates #36938
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants