[
https://issues.apache.org/jira/browse/AVRO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082657#comment-14082657
]
Doug Cutting commented on AVRO-739:
-----------------------------------
I don't have a strong opinion on the single versus dual attribute approach.
Are there features we want to support that will be substantially helped or
hindered by one or the other? From a simplicity point of view, a single
attribute is attractive.
Whether we opt for simple names ("date", "time") or those that also include the
encoding ("unix-epoch-millis") depends on what we wish to distinguish them
from. If we think we'll primarily support only a single timestamp
representation then a simple name like "timestamp" suffices. If we think we
may need to support multiple kinds of epochs, then putting the epoch type in
the name is probably wise. My guess is that we should standardize on a single
epoch and set of types compatible with SQL and Parquet, and use the simplest
names that achieve that.
> 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)
