-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
fix #35262 define deprecations of API's as a whole and urls #39063
fix #35262 define deprecations of API's as a whole and urls #39063
Conversation
Pinging @elastic/es-core-infra |
@bmcconaghy will this affect Console? as @jasontedor noted need to update PR and I still need to make the version qualified up to the path (major.minor.patch) |
ab35d03
to
477f99d
Compare
8f181dd
to
10d0836
Compare
…e body which is a safer behaviour as well
10d0836
to
430108a
Compare
run elasticsearch-ci/1 |
1 similar comment
run elasticsearch-ci/1 |
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.
LGTM. We need to have an answer regarding console prior to merging
@@ -2,6 +2,10 @@ | |||
"indices.exists_type": { | |||
"documentation": "http://www.elastic.co/guide/en/elasticsearch/reference/master/indices-types-exists.html", | |||
"methods": ["HEAD"], | |||
"deprecated" : { | |||
"version" : "7.0.0", | |||
"description" : "Types are being removed from elasticsearch and therefor this API is on the way out. Read more here: https://www.elastic.co/guide/en/elasticsearch/reference/master/removal-of-types.html" |
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.
"description" : "Types are being removed from elasticsearch and therefor this API is on the way out. Read more here: https://www.elastic.co/guide/en/elasticsearch/reference/master/removal-of-types.html" | |
"description" : "Types are being removed from elasticsearch and therefore this API is on the way out. Read more here: https://www.elastic.co/guide/en/elasticsearch/reference/master/removal-of-types.html" |
Sorry, somehow did not see this ping from before. Console is not directly connected to the ES REST specs, so it will not affect console. The parser that generates the JSON for the console autocomplete will not mind that there are new attributes in these either. Console has no mechanism for warning users that endpoints are deprecated, so it could not (currently) consume them to warn users that things are going away. However, it does display deprecation warnings coming back in ES responses, so if these deprecated paths return warnings the user will be notified. |
* fix #35262 define deprecations of API's as a whole and urls * document hot threads deprecated paths * deprecate scroll_id as part of the URL, documented only as part of the body which is a safer behaviour as well * use version numbers up to patch version * rest spec parser picks up deprecated paths as paths too (cherry picked from commit 7e06023)
…lastic#39063) * fix elastic#35262 define deprecations of API's as a whole and urls * document hot threads deprecated paths * deprecate scroll_id as part of the URL, documented only as part of the body which is a safer behaviour as well * use version numbers up to patch version * rest spec parser picks up deprecated paths as paths too
This moves deprecated paths out of
paths
and into a new property calleddeprecated_paths
.This allows client generators to either skip or otherwise mark these endpoints as deprecated/obsolete and use language specific mechanisms to warn the users.
This also introduces a
deprecated
block on the API itself to mark a whole API as deprecated. Seeindices.exists_type.json