[ML][Data Frame] have DataFrameTransformConfigUpdate#apply set Version #45391
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Pinging @elastic/ml-core |
|
run elasticsearch-ci/1 |
2 similar comments
|
run elasticsearch-ci/1 |
|
run elasticsearch-ci/1 |
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this pull request
Aug 9, 2019
benwtrent
added a commit
that referenced
this pull request
Aug 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumping the version on update allows transforms that are updated, then stopped/started to be assigned to new nodes. This is so we can handle the case when an
_updateadds fields that older nodes don't recognize.closes #45389