Skip to content
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

DRAFT [META] REST Compatible API V7 completeness #68905

Closed
pgomulka opened this issue Feb 11, 2021 · 2 comments
Closed

DRAFT [META] REST Compatible API V7 completeness #68905

pgomulka opened this issue Feb 11, 2021 · 2 comments

Comments

@pgomulka
Copy link
Contributor

pgomulka commented Feb 11, 2021

REST Compatible API v7 completeness

As described in #51816 all breaking changes could be subject to applying some compatibility at the REST layer to assist with upgrades. This issue exists to ensure that there is a complete and exhaustive list of all breaking changes and make the determination REST API compatibility should be applied.

A complete list of all breaking changes categorized by

  • Requires REST API compatibility with v7
  • Does not require REST API compatibility with v7
  • Unsure - needs more investigation (temporary status while we work through the list)
  • Potentially leverage REST API compatibility, but out of immediate scope

The number of check boxes here should equal number of closed issues from this query:
Eldest to newest breaking changes

Each line item should have a independent validation, and line items that require changes should be linked to the associated PR and issues. For specific compatibilities that require discussions, please open a new issue (as opposed to the comments of this issue).

Requires REST API compatibility with v7

Misc

//TODO: break up into better categories

Types

These are mostly managed by #54160. The issues here match 1:1 to the issues with >breaking label to help ensure the counts of breaking changes and number of checkboxes are equal.

Mappings

Unsure - needs more investigation

Potentially leverage REST API compatibility, but out of immediate scope

scripting

EQL

Does not require REST API compatibility with v7

Setttings

Settings are not subject to REST API compatibility. Often the changes behind the settings represent some behavior that is not carried forward.

Validation

Additional or stricter validation is a type of breaking change that can change the response of a request from a success to a specific failure. However, success -> error responses are not covered by REST API compatibility and is considered behavior.

Is actually breaking for 8.0 ?

Perhaps mislabeled or was beta/experimental and/or change was made in a minor

Misc

@pgomulka pgomulka added :Core/Infra/REST API REST infrastructure and utilities Meta v8.0.0 labels Feb 11, 2021
@elasticmachine elasticmachine added the Team:Core/Infra Meta label for core/infra team label Feb 11, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@pgomulka pgomulka changed the title [META] REST Compatible API V7 completness DRAFT [META] REST Compatible API V7 completness Feb 11, 2021
@pgomulka pgomulka removed :Core/Infra/REST API REST infrastructure and utilities Team:Core/Infra Meta label for core/infra team labels Feb 11, 2021
@joegallo joegallo changed the title DRAFT [META] REST Compatible API V7 completness DRAFT [META] REST Compatible API V7 completeness Mar 2, 2021
@joegallo
Copy link
Contributor

re: Remove Repository Stats API #62309: see #62309 as well as #62297 and #62308 -- this was /_snapshot/{repository}/_stats and as @tlrx observed "we're talking about an experimental API that was never released(behind a feature flag)." I think it's fair to assume we will not need to cover this via REST compatibility. @jakelandis do you concur?

droberts195 added a commit to droberts195/elasticsearch that referenced this issue Sep 7, 2021
Related to elastic#51816 / elastic#68905.

Adds back the _xpack/ml routes when using rest compatibility for a request.
droberts195 added a commit that referenced this issue Sep 14, 2021
Related to #51816 / #68905.

Adds back the _xpack/ml routes when using rest compatibility for a request.
@arteam arteam added v8.1.0 and removed v8.0.0 labels Jan 12, 2022
@mark-vieira mark-vieira added v8.2.0 and removed v8.1.0 labels Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants