[ML] Updating detectors should not affect existing job #32040
Merged
+35
−11
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
This is a light backport of elastic#31957 for 6.3.
|
Pinging @elastic/ml-core |
davidkyle
approved these changes
Jul 13, 2018
| Job updatedJob = update.mergeWithJob(job, new ByteSizeValue(0L)); | ||
|
|
||
| assertThat(updatedJob.getAnalysisConfig().getDetectors().get(0).getRules(), equalTo(rules)); | ||
| assertThat(job.getAnalysisConfig().getDetectors().get(0).getRules().isEmpty(), is(true)); |
There was a problem hiding this comment.
There is an empty() matcher - org.hamcrest.Matchers.empty
dimitris-athanasiou
deleted the
updating-detectors-should-not-affect-existing-job
branch
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.
This is a light backport of #31957 for 6.3.