[
https://issues.apache.org/jira/browse/AVRO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089855#comment-14089855
]
Skye Wanderman-Milne commented on AVRO-739:
-------------------------------------------
I realize I'm chiming in a little late, but I would strongly prefer a single
binary encoding for each type (rather than both a human-readable and binary
encoding). The extra string encodings seem like an unreasonably high price to
pay in development and test effort for human-readable output (I count 4 extra
type/logicalType pairs that need to be implemented by every library/application
implementing the spec). I think we'll end up with very few
libraries/applications implementing all of the types and encodings, which is
bad for interop whether you're using Avro for storage or IPC. And once it's in
the spec, we won't be able to scale back to a smaller, easier-to-maintain
option.
>From a more ideological perspective, I don't think it's always a good idea to
>offer more choices. Instead of having users choose between performance and
>human-readability (and realistically between which applications will be able
>to read their data), maybe it would make more sense to only use the binary
>encoding and provide a tool for dumping the data in a human-readable format.
(As to why I would prefer only the binary encoding and not only the string
encoding: not only is the binary encoding more performant, I think we'll see
fewer bugs/incompatibilities around what constitutes a valid date/time string).
> 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.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
