[ML] Fixes recognizer job wizard to use dedicated index setting #25706
Conversation
This file contains hidden or 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
peteharverson
added
review
release_note:fix
v7.0.0
:ml
Feature:Anomaly Detection
peteharverson
requested review from
alvarezmelissa87,
jgowdyelastic and
walterra
Contributor
|
Pinging @elastic/ml-ui |
Contributor
💚 Build Succeeded |
peteharverson
added a commit
to peteharverson/kibana
that referenced
this pull request
Nov 15, 2018
peteharverson
added a commit
that referenced
this pull request
Nov 15, 2018
peteharverson
added a commit
to peteharverson/kibana
that referenced
this pull request
Nov 21, 2018
peteharverson
added a commit
that referenced
this pull request
Nov 23, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Summary
Fixes the data recognizer job wizard to use the 'Use dedicated index' checkbox setting. The checkbox value is now passed through to the server-side code which creates the job configuration, adding a
results_index_nameproperty if the checkbox is ticked.Previously this setting was not being passed through to the server-side endpoint, so a dedicated index would never be created. Dedicated indexes need to be used, for example, to avoid mapping conflicts where a field already exists with the same name but a different mapping in the shared results index:
Checklist
For maintainers