-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[ES body
removal] @elastic/kibana-data-discovery
#204881
Closed
afharo
wants to merge
11
commits into
elastic:main
from
afharo:esclient/remove-deprecated-body/elastic/kibana-data-discovery
Closed
[ES body
removal] @elastic/kibana-data-discovery
#204881
afharo
wants to merge
11
commits into
elastic:main
from
afharo:esclient/remove-deprecated-body/elastic/kibana-data-discovery
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
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
…-deprecated-body/elastic/kibana-data-discovery
…-deprecated-body/elastic/kibana-data-discovery
…-deprecated-body/elastic/kibana-data-discovery
💔 Build Failed
Failed CI Steps
Test Failures
Metrics [docs]Async chunks
Page load bundle
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
cc @afharo |
Closing in favor of #208776 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
elasticsearch-js-9
release_note:skip
Skip the PR/issue when compiling release notes
Team:DataDiscovery
Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Team:Defend Workflows
“EDR Workflows” sub-team of Security Solution
Team:Threat Hunting:Explore
Team:Threat Hunting:Investigations
Security Solution Investigations Team
Team:Threat Hunting
Security Solution Threat Hunting Team
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
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.
Summary
in preparation for 9.0, we're trying to remove the deprecated
body
param in the ES client.To make it easier to review, the changes have been split into multiple PRs, trying to group them per code owner as much as possible.
However, unfortunately, due to cross-dependencies, your team may be pinged more than once. Apologies for that additional noise.
What changes?
Nothing changes internally. The ES client already places everything where it should be when performing the request to ES (URL vs. query string vs. body params).
The main change is in the usage: when using the JS ES client, developers don't need to identify what goes in the body and what goes in the URL. All settings are provided at the root level. So, in summary, the change is:
Some exceptions to this rule:
body
array withoperations
array (direct replacement)body
array withsettings
(direct replacement)