-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate allow_no_jobs and allow_no_datafeeds in favor of allow_no_match #60601
Merged
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
przemekwitek
force-pushed
the
allow_no_match
branch
from
August 4, 2020 09:29
3c68b7e
to
37983fa
Compare
przemekwitek
changed the title
[DRAFT] Rename allow_no_jobs to allow_no_match and allow_no_datafeeds to allow_no_match
Rename allow_no_jobs to allow_no_match and allow_no_datafeeds to allow_no_match
Aug 4, 2020
przemekwitek
force-pushed
the
allow_no_match
branch
from
August 4, 2020 10:00
37983fa
to
c3bd05b
Compare
run elasticsearch-ci/bwc |
przemekwitek
added
:ml
Machine learning
>breaking-java
>refactoring
v7.10.0
v8.0.0
labels
Aug 4, 2020
Pinging @elastic/ml-core (:ml) |
przemekwitek
changed the title
Rename allow_no_jobs to allow_no_match and allow_no_datafeeds to allow_no_match
Deprecate allow_no_jobs and allow_no_datafeeds in favor of allow_no_match
Aug 4, 2020
benwtrent
reviewed
Aug 4, 2020
x-pack/plugin/src/test/resources/rest-api-spec/api/ml.stop_datafeed.json
Show resolved
Hide resolved
...in/ml/src/main/java/org/elasticsearch/xpack/ml/rest/results/RestGetOverallBucketsAction.java
Show resolved
Hide resolved
benwtrent
approved these changes
Aug 4, 2020
lcawl
approved these changes
Aug 5, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docs LGTM, thanks!
przemekwitek
force-pushed
the
allow_no_match
branch
from
August 5, 2020 09:42
441ca38
to
08aea5a
Compare
przemekwitek
added a commit
to przemekwitek/elasticsearch
that referenced
this pull request
Aug 5, 2020
przemekwitek
added a commit
that referenced
this pull request
Aug 5, 2020
61 tasks
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 PR deprecates
allow_no_jobs
andallow_no_datafeeds
API parameters in favor ofallow_no_match
.The old parameters are still accepted by the APIs but the deprecation warning is emitted if the old parameter name is used in the request body or as a request param.
High-level REST client classes will now send the new
allow_no_match
parameter to the backend.Closes #60642