-
Notifications
You must be signed in to change notification settings - Fork 129
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
New client is coming to town #63
Comments
😭 @delvedor do you know alternatives? |
just switch to it? |
Is there any update on when this package will move to the new ES client implementation? |
To anyone looking for the updated version, here is a sample gist[0] that fit our requirements. [0] https://gist.github.com/parthdesai93/1bd3a25ad4cf788d49ce4a00a1bb3268 |
Any updates on this? |
I'm also interested. Any updates? |
#following |
So, I made a fork and took care of this. https://github.com/compwright/aws-elasticsearch-connector |
We've released an NPM package that works with @elastic/eleasticsearch and AWS elasticsearch clusters. It signs the requests for AWS and refreshes the credentials when they're about to expire. https://www.npmjs.com/package/@acuris/aws-es-connection |
Hello! Thank you for keeping up this work!
We are working on a new JavaScript client for Elasticsearch, and you can find the work in elastic/elasticsearch-js#next, the new client will replace the current one, which will be deprecated.
The code has been rewritten from scratch, so your current implementation will not be compatible.
Please let me know if you have any question :)
The text was updated successfully, but these errors were encountered: