Support ES client version upgrade to v8.0 #108387
Labels
Feature:elasticsearch
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
v8.0.0
You can find the full Elasticsearch client roadmap here elastic/elasticsearch-js#1542
There are a few things that may require additional work from the Core side:
Remove the body key from the request
. effort for Core:Small
, providing the client gives a long migration period for the legacy style, otherwise it affects nearly all the usages in Kibana codebase.The returned value of API calls is the body and not the HTTP related keys
. effort for Core:Small
, providing client allows Kibana to specify{ meta: true }
on the client level and shipskibana.d.ts
withApiResponse
-comptible typings.@elastic/elasticsearch
client continue shipping a Kibana-specificd.ts
to support7.x
-compatible interfaces by default. After8.0
we can consider an option to allow plugins to specifymeta:false
to returnbody
as response.Migrate to the "undici" http client
. We need to investigate what incompatibilities Kibana might have with the configuration parameters of the new http agent. The ES client supports configuring what http client should be used. To be on the safe side, we can continue using the nativehttp
agent. Migration to theundici
agent can be done in a follow-up PR.kibana/src/core/server/elasticsearch/client/client_config.ts
Lines 22 to 38 in 3950c43
Rename ssl option to tls
effort for Core:Small
, we aren't going to renameelasticsearch.ssl
config, just handle the renaming internally.Move from emitter-like interface to a diagnostic method
effort for Core:Small
The text was updated successfully, but these errors were encountered: