Florian Bernd
Florian Bernd
Related: #7998
@ModernBlacksmith Could you please confirm that this bug is fixed in the latest 8.13.x version of the client? @GuyTraveler NEST has been deprecated and will be end-of-life at the end...
I see multiple problems here. During deserialization: ```json { "...": "...", "aggregations": { "filters#bucket_name": { "buckets": { "color_filter": { "doc_count": 0 } } }, "sterms#color_aggregate": { "doc_count_error_upper_bound": 0, "sum_other_doc_count": 0,...
This is fixed in 8.13.x.
Hi @giorgos-papanikos, your issue and the linked one are both different cases. I'll investigate tomorrow why we get keyed results here instead of a flat list.
@giorgos-papanikos No worries for linking the unrelated issues. It's always appreciated if users check for related issues first 🙂 Regarding the `keyed` situation: The client explicitly does not want keyed...
Hi @giorgos-papanikos, yes that essentially summarizes my idea. The result will always be a flat list, but the `key` property will be available if the user has utilized the dictionary...
Hi @MackMendes just to clarify. If you set a breakpoint on your custom `Serialize` function, it doesn't get hit?
Hi @MackMendes, please have a look at this comment: https://github.com/elastic/elasticsearch-net/issues/3517#issuecomment-473359744 This describes how to achieve your goal in a slightly different/easier way.
Hi, I'll keep this as a NEST bug until I have time to check in detail. NEST does not have the highest priority at the moment. In the meantime I...