-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Custom SourceSerializer options not effective for response data #8075
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Hi @chaimtevel, thanks for reporting! I'll have a look at this right away 🙂 |
flobernd
added a commit
that referenced
this issue
Apr 4, 2024
flobernd
added a commit
that referenced
this issue
Apr 4, 2024
Closes #8075 Co-authored-by: Florian Bernd <[email protected]>
flobernd
added a commit
that referenced
this issue
Apr 4, 2024
Closes #8075 Co-authored-by: Florian Bernd <[email protected]>
Thanks for the nice issue description and the reproducer! Fixed in 8.13.1. |
Thank you so much! We rely on this library heavily so we're happy to help in any way we can. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Elastic.Clients.Elasticsearch version: 8.13.0
Elasticsearch version: 8.9.1
.NET runtime version: 8.0
Operating system version: Windows
Description of the problem including expected versus actual behavior:
We're really were excited to see the latest release which has added support for all aggregations. As I was testing I came across this issue. When adding custom converters to
DefaultSourceSerializer
, they do not seem to be taking effect when reading response data.In the snippet below we're using a custom json converter for
System.Net.IPAddress
. When writing the data to the index the serializations works as expected but when reading the response data to a search request we get aUnexpectedTransportException
.Expected behavior
For the custom converters to be used to deserialize response data. This does appear to work in
Elastic.Clients.Elasticsearch
version 8.12.1Provide
DebugInformation
(if relevant):Here is a sample app I tested using Linpad:
The error message is
The JSON value could not be converted to System.Net.IPAddress. Path: $.hits.hits[0]._source.ipAddress | LineNumber: 22 | BytePositionInLine: 35.
I've attached the debug information.
custom-serialization-debug-info.txt
Thanks!
Chaim
The text was updated successfully, but these errors were encountered: