[ML] Create the ml-config index#36792
Merged
davidkyle merged 2 commits intoelastic:6.xfrom Dec 18, 2018
Merged
Conversation
Collaborator
|
Pinging @elastic/ml-core |
🚀 
davidkyle
added a commit
to davidkyle/elasticsearch
that referenced
this pull request
Dec 19, 2018
davidkyle
added a commit
that referenced
this pull request
Dec 19, 2018
This was referenced Jan 16, 2019
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
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.
Create the .ml-config index in the migrator class if it does not exist and require the existence of the index for the jobs/datafeeds are eligible to be migrated checks. The index is created only if there are job and datafeed configs to migrate.
The created index has index.max_result_window explicitly set to 10,000 and the template has the same setting. The classes that search the index for configs use that value to set the search size.
Marked as non issue for docs changes as it will be document as part of #36698
Addressed #34864