[DOCS] Re-enable code snippet testing in close anomaly detection job API #48259
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
|
Pinging @elastic/ml-core (:ml) |
|
Pinging @elastic/es-docs (>docs) |
47 tasks
lcawl
added a commit
to lcawl/elasticsearch
that referenced
this pull request
Oct 28, 2019
lcawl
added a commit
to lcawl/elasticsearch
that referenced
this pull request
Oct 28, 2019
lcawl
added a commit
to lcawl/elasticsearch
that referenced
this pull request
Oct 28, 2019
This was referenced Oct 28, 2019
lcawl
added a commit
that referenced
this pull request
Oct 28, 2019
lcawl
added a commit
that referenced
this pull request
Oct 28, 2019
lcawl
added a commit
that referenced
this pull request
Oct 28, 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.
The current code snippet tests in the documentation do not seem to support the use of non-OSS APIs and result in "rest api xxx doesn't exist in the rest spec" failures. This PR therefore tries to use "raw" methods in the build.gradle to re-enable testing in a machine learning API, similar to what is done for rollup and transform APIs (#45154).