Florian Bernd

Nevermind, I just identified the issue.

Hi @schoder-moreno, this is currently not on my roadmap, but sounds like a useful feature. I have to check how this was implemented in NEST and how much effort it...

Hi @niemyjski , I think this boils down to a code generator optimization which I've already planned in the corresponding (private) repository. A Term query, for example, requires 2 mandatory...

Hi @niemyjski, I don't want to expose the `AdditionalPropertyName` field for the reasons I stated in the other issue. However, we can happily add a `SortKey` property that just reflects...

Hi @niemyjski, This sounds like a very specialized use-case that might not be required for 99% of the users. Isn't that something that could easily be implemented by the user...

Hi @niemyjski, this is a difficult one. In ES, property objects do not hold their names. They are always used as part of a dictionary (`Properties` type in the new...

I just double checked and saw that `Properties` implements `IEnumerable` which means that the reverse lookup could be done using this interface. Given that fact, I think that a custom...

@niemyjski The Elasticsearch API uses `Dictionary` in almost all (but not really all) cases since the `Property` type itself (as defined by Elasticsearch) does not contain its own name. NEST...

Hi @niemyjski, this works fine for `Query`, if you omit the `_ =>`: ```csharp var query = new QueryDescriptor() .Term(t => t .Field("user.id") .Value("kimchy") ); var response = await client.SearchAsync(s...

Hi @deinman, bringing back the `JsonNetSerializer` is currently not on the roadmap. It's currently unreleased as we did not have the capacity to thoroughly test it with the new client....