Florian Bernd

Hi @braveyp, these responses are generated from our specification. The specification closely maps the server-side of things and there simply is no common base class. We could potentially introduce a...

Hi @sneves, thanks for reporting. So basically MASM syntax uses `bcst` instead of `ptr` to indicate broadcasting and as well omits the regular Intel style broadcast decorator.

Hi @tommymonk , nested mappings do still support generics, but they always operate on the top-level type: ```csharp client.Indices.PutMappingAsync(x => x .Properties(x => x .Nested(p => p.OtherPerson, x => x...

It might be worth adding overloads for the nested mappings. We sadly lost a bit of convenience here and there with the new auto-generated client. Auto mapping is something still...

Hi @gpetrou, This got even easier now: ```csharp ElasticsearchClientSettings elasticsearchClientSettings = new( nodePool, sourceSerializer: (defaultSerializer, settings) => new DefaultSourceSerializer(settings, options => options.Converters.Add(/*...*/))); ``` Please let me know, if that answers...

Updating the action to a better supported one is probably a good idea. However, what I can tell from a quick check, the root of the error seems to be...

Hi @gpetrou, the generator flattens alias types like `Field` in responses as that makes usage easier in most cases. This place is special as that prevents us from passing the...

Hi @gpetrou, thanks for reporting. I'll check on Monday.

This seems to be the same issue as here: https://github.com/elastic/elasticsearch-java/issues/667

Our transport library `Elastic.Transport` is still in "pre-release" state (0.x.x version) which is bad, looking at this issue and other problems caused by the breaking changes that propagate to the...