Migrate elasticsearch-js-legacy to elasticsearch-js

[nsano-rururu]

elasticsearch-js-legacy to elasticsearch-js
https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/8.0/changelog-client.html
https://www.npmjs.com/package/elasticsearch

This package has been deprecated
This client is no longer maintained. We strongly advise you to migrate to the new Elasticsearch client.

[Karql]

Thanks.

I will check it but this has low prio. Probably nobody use it 😏

[nuno-andre]

Elastic has docs about migrating from the legacy JS client to the new one.

[nsano-rururu]

npm WARN deprecated elasticsearch@16.7.3: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

[nsano-rururu]

elasticsearch-js-legacy is a JavaScript client library that supports older versions of Elasticsearch (6.x and 7.x). As Elasticsearch versions evolve, the new library @elastic/elasticsearch is recommended. The following are disadvantages of continuing to use elasticsearch-js-legacy.

1. Support may have ended
   elasticsearch-js-legacy supports older versions of Elasticsearch, so it is not compatible with the latest Elasticsearch versions (8.x and later). It is likely that official support has ended, and new bug fixes and security patches may not be provided.

2. New features not available
   elasticsearch-js-legacy does not support features and improvements in new versions of Elasticsearch. This includes new APIs, performance improvements, and security enhancements.

3. Dependency updates are delayed
   Depending on older versions makes it difficult for libraries and dependencies to be updated, which can cause security and performance issues. In particular, old libraries may no longer work when dependent packages or Node.js itself are updated to new versions.

4. Ecosystem Integrity
   New versions of the @elastic/elasticsearch client are optimized for the latest Elasticsearch features and integrate smoothly with other Elastic Stack tools (Kibana, Beats, etc.). Continuing to use older libraries can cause issues with consistency with the rest of the ecosystem.

5. Performance Issues
   New client libraries offer improved performance and efficiency. Using older libraries means you miss out on these improvements.

6. Community and Documentation Delays
   elasticsearch-js-legacy is no longer in common use, so you may find it has less community support and documentation. This can make it take longer to resolve issues.
   Conclusion
   If you are currently using Elasticsearch 6.x or 7.x and are not planning to upgrade anytime soon, staying with elasticsearch-js-legacy may be an option. However, in the long run, it is better to consider migrating to @elastic/elasticsearch for security, performance, and features.

[joelsdc]

Hey guys, it's been a while since the last comment. Can I kindly ask for an update on this?

[Karql]

As I mentioned above,
I personally don't use these functionalities.

They are remnants from the original project.

In my opinion, the only use case that makes sense is the metadata controller.

The others, like search, could potentially be a security risk, as they merely act as a proxy to Elasticsearch.

Do you use any of these functionalities? Describe their use cases.