-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Comments
pgomulka
added
:Core/Infra/REST API
REST infrastructure and utilities
Meta
v8.0.0
labels
Feb 11, 2021
Pinging @elastic/es-core-infra (Team:Core/Infra) |
pgomulka
changed the title
[META] REST Compatible API V7 completness
DRAFT [META] REST Compatible API V7 completness
Feb 11, 2021
pgomulka
removed
:Core/Infra/REST API
REST infrastructure and utilities
Team:Core/Infra
Meta label for core/infra team
labels
Feb 11, 2021
joegallo
changed the title
DRAFT [META] REST Compatible API V7 completness
DRAFT [META] REST Compatible API V7 completeness
Mar 2, 2021
re: |
This was referenced Apr 2, 2021
This was referenced Jun 7, 2021
This was referenced Aug 4, 2021
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
This was referenced Jan 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
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
cutoff_frequency
we could simply allow to parse these but do nothing. But forCommonTermsQuery
it looks more complex and I am not sure how to implement this without bringing too much code back.only_expunge_deletes
andmax_num_segments
set Force Merge should reject requests withonly_expunge_deletes
andmax_num_segments
set #44761Types
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.type
query Removetype
query #47207include_type_name
parameter from REST layer Removeinclude_type_name
parameter from REST layer #48632Mappings
Unsure - needs more investigation
exclude_generated
that removes generated fields in GET config APIs [ML] add new flagexclude_generated
that removes generated fields in GET config APIs #63899Potentially leverage REST API compatibility, but out of immediate scope
scripting
EQL
=
for comparisons EQL: Remove support for=
for comparisons #62756Does 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.
_field_names
enabled setting Disallow_field_names
enabled setting #46681Validation
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.
discovery.seed_hosts
#41404Is actually breaking for 8.0 ?
Perhaps mislabeled or was beta/experimental and/or change was made in a minor
force
flag from _start [ML][Transforms] removeforce
flag from _start #46414 (feature was beta when this change was made)Misc
delimited_payload_filter
#43686 (behavior)The text was updated successfully, but these errors were encountered: