[
https://issues.apache.org/jira/browse/AVRO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105869#comment-14105869
]
Ryan Blue commented on AVRO-739:
--------------------------------
[~cutting], is there a specific use case you have in mind that will perform
poorly when durations are encoded in little-endian and sorted byte-wise?
I think it should be okay to use little-endian because there isn't a
well-defined sort order for durations. Each value is independent and there's no
requirement for conversion. (1, 0, 0) and (0, 30, 0) are incomparable because
sometimes 1 month is longer than 30 days and sometimes shorter, depending on
the start time the interval is applied to. Big-endian would produce results
that are generally grouped by similarity and size, but I think it's more
important to match the format used elsewhere (if its reasonable) and Parquet
uses little-endian.
> 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-update-spec.diff, AVRO-739.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
