[
https://issues.apache.org/jira/browse/AVRO-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242524#comment-16242524
]
Ryan Blue commented on AVRO-2021:
---------------------------------
[~nkollar], thanks for pointing out this issue.
I think we should revisit this. Logical types in the spec are defined for
additional (and optional) interoperability between Avro implementations and
systems that use Avro. We want to generally keep the set of logical types small
and well-defined to avoid putting so many requirements out there that nothing
actually implements them. The UUID type in Java is an example of this. There is
no real benefit to defining the UUID logical type in the spec, unless we want
to define how it should be stored. Instead, the UUID logical type in Java is an
example of how you can use the logical types API in Java to convert between
representations.
If we want to define how a UUID should be stored, as a 16-byte fixed, then I
think that makes sense. Otherwise, we're defining how UUIDs should be stored
for interoperability and specifying a requirement that is both inefficient and
obvious. Any interest in updating this to use a 16-byte fixed? If not, I think
we should remove this before it makes it into a release.
> uuid logical type is not documented
> -----------------------------------
>
> Key: AVRO-2021
> URL: https://issues.apache.org/jira/browse/AVRO-2021
> Project: Avro
> Issue Type: Improvement
> Reporter: Andrew Rosca
> Assignee: Nandor Kollar
> Priority: Minor
> Fix For: 1.9.0, 1.8.3
>
> Attachments: AVRO-2021_1.patch
>
>
> The documentation does not mention anything about the _uuid_ logical type,
> which is in fact implemented in LogicalTypes.java.
> Add documentation for _uuid_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
