avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-739) Add Date/Time data types
Date Tue, 10 Sep 2013 16:40:54 GMT

    [ https://issues.apache.org/jira/browse/AVRO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763187#comment-13763187
] 

Doug Cutting commented on AVRO-739:
-----------------------------------

> One could log another field with the timezone identifier for these.

>From my understanding of SQL, for TIMETZ and TIMESTAMPTZ columns, a separate timezone
is not stored per row.  Rather, the TZ in the schema only affects how dates are parsed and
displayed.  Am I wrong?  If I am correct, then the timezone should not be a field but a schema
attribute that's used by implementations when parsing and displaying values.  In all cases
I believe we should only store a single UTC timestamp per value.  Adding a distinct primitive
type for each parsing/display variant seems like a poor design choice.

> A long in binary form makes sense, but in JSON, an ISO8601 string might be more useful.

Special-casing this would rule out back-compatibility, no?
                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message