Hi,
(let me know if this is not the right place to post ElasticSearch.Net
questions).
I'm indexing a document of type "User" through ElasticSearch.Net with this
command (key is a string guid):
client.Index<User>(index, "user", key, user);
This invokes the serializer and stores the json in my ES cluster, as
expected. ElasticSearch responds with this json:
{\
"_index\":\"users_2014_09\",\"_type\":\"user\",\"_id\":\"M8k_6WLTtESlYod8-CDUXw_P4wXE0OkkvprjRiqGP1bqQ\",\"_version\":1,\"created\":true}
Now the strange thing is that the ElasticSearch.Net client tries to
deserialize this result as a "User" object. Normally this deserialization
method will return null and not create any visible side-effects, but in my
case I'm using the field "created" as a DateTime field, and the
deserialization throws a nasty error.
My question is: Why on earth does the client spend energy deserializing a
response to an Index command, and into the wrong type? This looks like a
bug.
Thanks,
Lasse
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/1bfff890-ae3d-422f-b12b-54548cf01f62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
