Florian Bernd

Hi @bonny-bonev, some of the convenience features are not yet ported over from 7.x to 8.x. My primary focus is on endpoint support at the moment (there is still a...

Hi @mcdis, AOT compilation is not supported at the moment. There must be a `JsonSerializerContext` for both, the source- and the request/response serializer. The later one is internal. Besides that,...

Hi @mcdis, thanks for the code examples! Besides the (de-)serialization part, we as well use reflection in other parts of the library. I would have to check all these places,...

> on porting to NativeAOT, several of my cents Thanks to you as well! I know how to get around most of the issues, but at the moment it's just...

Hi @giannik, You are right, KNN queries are not completeley implemented yet. I can not give you an exact ETA for that, as it currently does not have very high...

@giannik This scenario is not directly supported by the client. If you have query payloads in JSON format, I would probably use the low level transport client to send raw...

@giannik There is a very short example in this migration guide document: https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/migration-guide.html#_workarounds_for_missing_features Deserializing back to the CLR response types is more complex and I currently don't have any read-to-use...

KNN queries are now fully supported in 8.13.x.

Hi @KPGDL, this could be a change in behavior that was introduced by switching to `System.Text.Json` as the default JSON (de-)serializer. (Edited my answer as I incorrectly though you were...

Hi @dlukyanov, thanks for reporting! From a first glance, it seems we forgot to annotate the `RawJsonString` to use the `RawJsonConverter`.