-
Notifications
You must be signed in to change notification settings - Fork 906
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
OpenSearch Dashboards: Consolidation of clients as part of version decoupling #3900
Comments
Following are the list of functions, interfaces and type definitions that are using legacy elasticsearch client properties and methods within the Opensearch Dashboard repo -
|
List of Opensearch Dashboards core plugins currently using Elasticsearch legacy client methods:
List of packages in OSD currently using Elasticsearch legacy client methods:
|
Aliasing elasticsearch to npm:@opensearch-project/[email protected]
Params type mismatch in Elasticseach client modules vs Opensearch client modules.
|
|
As part of version decoupling project, one of the pre-req task is to consolidate all the clients usages in Opensearch Dashboards which interacts with Opensearch.
Reference: #3095
Decoupling OpenSearch Dashboards and OpenSearch
Various components of OpenSearch Dashboards interact with OpenSearch using one of three unrelated methods: the legacy client, the OpenSearch client, and direct HTTP calls.
Proposed Solution
Make OpenSearch Dashboards rely solely on the Node.js client, @opensearch-project/opensearch, and delegate the responsibility of interacting with OpenSearch to it. The Node.js client is a low-level library that could be compatible with more that one major version of OpenSearch and any variations would be normalized by a wrapper (introduced below). OpenSearch Dashboards will be instructed to use the latest compatible major version of the Node.js client available. This involves replacing the components that consume the legacy elasticsearch client and the direct HTTP channel with method that call the official Node.js client.
Requirement:
[email protected]
npm usages and replace it with opensearch-js client.The text was updated successfully, but these errors were encountered: