Tomas Della Vedova

Hello again! I’ve talked about this internally and we think that having a retry mechanism inside the client itself could be harmful and lead to some misunderstanding on how the...

Hello! Which version of the Client and Elasticsearch are you using? The client's code to get the certificate fingerprint is quite straightforward, so I doubt the issue might be in...

FYI: [`@elastic/transport`](https://github.com/elastic/elastic-transport-js) which is the engine of the [elasticsearch client](https://github.com/elastic/elasticsearch-js) uses `undici` by default from v8.

> Do you have any current plans to implement system indices support, or thoughts on whether or not it's something that belongs within the elasticsearch-js client? I'm not sure what...

Hello! Thanks for the tip! I'll look into this. Sidenote, bulk is not idempotent, as is an API used to perform write operations. Many read APIs are using POST tho,...

It depends on what you are doing. While `delete` and `create` operations are idempotent, `index` and `update` will at least update the document's `_version` field. While if you are sending...

> Thanks! Maybe we could dynamically check for those and set idempotent accordingly? Currently, we are not tracking which operations are idempotent and which aren't, so we can only detect...

Elasticsearch has no timeout or pipelining limit and sends no hints :)

> It is very important that the client fully consumes any and all response bodies. Might be worth to add to documentation if end-users are able to have streaming responses....

Other than "pass anything in an nested options object and surprise us.", what problems do you foresee here?