[
https://issues.apache.org/jira/browse/AVRO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094341#comment-14094341
]
Ryan Blue commented on AVRO-739:
--------------------------------
Good point about not being able to use conversion methods in situations like
debugging. But, I think I'd rather not have those limitations dictate the
possible representations when we'll end up with more to support and wasteful
formats. You also mention using specific objects with ZonedDateTime fields --
that addresses this problem by deserializing to a form that has a meaningful
toString representation, right? Maybe we should encourage that approach.
bq. Having said that, I absolutely don't insist on including these into spec -
just attempted to explain the reasons I am using them currently and have
initially suggested them.
Same here, I don't want to insist on anything. I just want to find a good
solution.
bq. Comments about adding "local" date-time and "High-precision" time in
addition to timestamp-millis are welcome.
For high-precision, what granularity do you think needs to be supported? Nanos?
Micros? We didn't have a clear answer on the Parquet side, which is why we
pushed high-precision from the original spec -- better to get some of the types
in and expand later. Maybe we should open a follow-up issue to discuss these?
> 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
> Fix For: 1.7.8
>
> Attachments: AVRO-739-datetime-spec.xml.patch,
> AVRO-739-datetime-spec.xml.patch, AVRO-739.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
