You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Ryan Blue (JIRA)" <ji...@apache.org> on 2016/08/03 20:29:20 UTC
[jira] [Commented] (AVRO-1893) UUIDs are deserialized into Strings
and not UUIDs
[ https://issues.apache.org/jira/browse/AVRO-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406565#comment-15406565 ]
Ryan Blue commented on AVRO-1893:
---------------------------------
It looks like you're using a different {{ReflectData}} instance to read and write. When you instantiate {{ReflectDatumReader}}, it uses {{ReflectData.get()}} but you've added the UUID type to {{ReflectData.AllowNulls.get()}}. You should use the same data model for both.
I also don't think it is a good idea to add conversions to the singleton instances of {{GenericData}} and subclasses, like {{ReflectData}}. If you want to change the conversions that are used, then I think the best practice is to create a new instance.
> UUIDs are deserialized into Strings and not UUIDs
> -------------------------------------------------
>
> Key: AVRO-1893
> URL: https://issues.apache.org/jira/browse/AVRO-1893
> Project: Avro
> Issue Type: Bug
> Reporter: Sachin Goyal
> Attachments: TestUuidFields.java
>
>
> Here is a test that shows UUIDs are deserialized back into a string instead of UUID.
> Applications would expect UUID fields in their objects instead of strings when avro reads them back.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)