[
https://issues.apache.org/jira/browse/AVRO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084061#comment-14084061
]
Dmitry Kovalev commented on AVRO-739:
-------------------------------------
Epochs and short names - I wasn't suggesting to support different ones, I just
mentioned this to illustrate why I thought longer, more descriptive names were
better. I still think they are, but I having read about Parquet etc I
understand where you are coming from.
I believe the different views come from the usage context - if you view Avro as
storage format for Hadoop only then I would agree that it makes sense to choose
a single, most compact representation as standard and this would improve
interop in the sense that every part of that ecosystem will only have to
support this single format.
However I am using Avro as an IPC protocol in an application which exchanges
complex data between services (saves me a lot of manual work as it supports
maps and unions and codegen on all platforms). From this perspective, I believe
that having standard type names for ISO8601-based representations of the above,
in addition to binary ones, would actually improve interop. This is because
people will want to use ISO-8601 in their protocols anyway (it is human
readable in JSON dumps, familiar to people with XML background etc). So I think
it is better to provide standard type names for these, rather than forcing to
either use binary representation or custom names.
So what would you say to the following: adopt Parquet names/specs for binary
representations, and add ISO-8601 string ones on top?
If you agree that this makes sense from both storage and IPC perspective then I
could draft it and post here as a documentation patch.
If you see ISO alternative representations as redundant or even evil then I
guess it means I cannot contribute anything else to this topic and will leave
it to you guys to sort out.
> Add Date/Time data types
> ------------------------
>
> Key: AVRO-739
> URL: https://issues.apache.org/jira/browse/AVRO-739
> Project: Avro
> Issue Type: New Feature
> Components: spec
> Reporter: Jeff Hammerbacher
> Attachments: AVRO-739.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
