-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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 _source_include
and _source_exclude
url parameters
#33475
Conversation
Pinging @elastic/es-search-aggs |
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.
I left something minor but this seems like the right way to do it to me.
Can anyone from @elastic/es-clients comment on the changes to the rest-api-spec?
sIncludes = request.param("_source_include", sIncludes); | ||
String sInclude = request.param("_source_include"); | ||
if (sInclude != null) { | ||
DEPRECATION_LOGGER.deprecated("Deprecated field [_source_include] used, expected [_source_includes] instead"); |
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.
What about replacing "field" with "parameter"?
I labelled this |
@elasticmachine, test this please |
`source_excludes` the deprecation message refers to `parameter` instead of `field`
"Deprecated _source_include and _source_exclude": | ||
|
||
- skip: | ||
version: " - 6.4.99" |
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.
// TODO consider changing the version (if needed) once the clients specs are changed to _source_includes
& _source_excludes
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.
I'd use 6.99.99 for now. After I merge this I'll backport it to the 6.x branch. Then I'll come in and update the range here to include the backport target version.
I'm fairly sure this is what caused the build to fail. If you crack open the PR build's full console it'll have a REPRODUCE WITH
line that should reproduce the failure. And I'm fairly sure switching this to 6.99.99 will make it go away.
@nik9000 thanks for the review! And starting the CI. I wonder why the high level REST client tests passed though. I guess I can look into this next ;) Should I assume that this PR will stay on hold until the clients change their specs? |
I'm happy to do it! Why the tests passed is a good question. If they are ignoring deprecation messages that'd be bad but a problem for another PR. Happy hunting!
They won't need to change their specs but they might need to do something. I'm not sure what. The .NET client generates things from these files. |
@nik9000 I just updated the PR to include the the strict deprecation mode and resolve the conflicts. |
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.
I left a request to change the line that I think caused the build to fail.
"Deprecated _source_include and _source_exclude": | ||
|
||
- skip: | ||
version: " - 6.4.99" |
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.
I'd use 6.99.99 for now. After I merge this I'll backport it to the 6.x branch. Then I'll come in and update the range here to include the backport target version.
I'm fairly sure this is what caused the build to fail. If you crack open the PR build's full console it'll have a REPRODUCE WITH
line that should reproduce the failure. And I'm fairly sure switching this to 6.99.99 will make it go away.
Thanks for updating this @lipsill! I think it is super close. Hopefully the |
@nik9000 thanks for the tip work around the issue;) Can you trigger another CI when you have the chance? |
@elasticmachine, test this please |
) Deprecates `_source_include` and `_source_exclude` url parameters in favor of `_source_inclues` and `_source_excludes` because those are consistent with the rest of Elasticsearch's APIs. Relates to #22792
@lipsill all merged and backported! Thanks so much for this! |
) Deprecates `_source_include` and `_source_exclude` url parameters in favor of `_source_inclues` and `_source_excludes` because those are consistent with the rest of Elasticsearch's APIs. Relates to #22792
Update the test for the deprecated `_source_exclude` parameter to run against 6.6.0+ now that we've backported the deprecation. Relates to #33475
Update the test for the deprecated `_source_exclude` parameter to run against 6.6.0+ now that we've backported the deprecation. Relates to #33475
This did end up biting us @nik9000 thank you for the ping though, not sure how it got lost on my end. |
Relates to #22792