Laurent Saint-Félix

Hi @AlexeyNikipelau Unfortunately what you get is coming from [golang transport](https://github.com/golang/go/blob/release-branch.go1.18/src/net/http/transport.go#L883) due to the fact that you are targeting a closed http port. I'll try to dig a bit deeper...

Hi @youngstone89 sorry for the late reply. There's indeed no way embedded to know which items were in the queue when an error is raised. You could however track the...

Hi @cmadarsh Thank you for reporting this! This is indeed a bug and should come with a proper serialization override to prevent such thing from happening. I'll have a look.

@cmadarsh I've just pushed a new [prerelease](https://github.com/elastic/go-elasticsearch/releases/tag/v8.4.0-alpha.2) with a fix related to the serialization which impact sort. Please test it and let me know if that works for you! As...

@cmadarsh A quick ping to let you know v8.4.0 has been released! Closing this.

That is a really cool idea, I'll tinker with the generator and will let you know !

That's an interesting idea, thank you for raising this. We could implement it as an option as this hugely depends on how you built your consumption of the body, if...

Thank you for the suggestion! This is definitely in the long term goals and would qualify as a helper to build specific queries. It would need to be built by...

@notque I'm not sure what your `FilterQuery` method does, however you can already do something like this: ```go s := &search.Request{Query: types.Query{Bool: types.BoolQuery{ Filter: []types.Query{ { Term: map[string]types.TermQuery{ "field": {Value:...

We're indeed missing some query parameters from within an expansion phase in the https://github.com/elastic/elasticsearch-specification I'll have a look and will regenerate the API when this is fixed.