-
Notifications
You must be signed in to change notification settings - Fork 729
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
What happened with connectionClass? #934
Comments
Hello! You are right, it's not mentioned in the document. Still, be aware that Connection classes written for the legacy client will not work with the new client. Since it looks like you are using the aws connection, take a look at TheDeveloper/http-aws-es#63 for more information. |
It seems like this Connection class expects one to override a synchronous, non-void A suggested solution was offered back in May, here, but it seems to A) leverage async/await (which I don't believe will work with this Connection class), and B) leverage an AWS.Signers namespace, which seems to be private, per this (and current experience). |
We understand that this might be important for you, but this issue has been automatically marked as stale because it has not had recent activity either from our end or yours. Note: in the past months we have built a new client, that has just landed in master. If you want to open an issue or a pr for the legacy client, you should do that in https://github.com/elastic/elasticsearch-js-legacy |
This is still very relevant to anyone using AWS ElasticSearch. |
Any work being done on this? |
Maybe, these packages will help: |
Hello, I would like to make use of the new client and while checking https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/breaking-changes.html there are no mentions of changes to
connectionClass
, however it does not seem to be the case and I am unable to replicate the following:Could you please advise how best to go around this or what I'm missing?
Cheers.
The text was updated successfully, but these errors were encountered: