[
https://issues.apache.org/jira/browse/AVRO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093371#comment-14093371
]
Ryan Blue commented on AVRO-739:
--------------------------------
bq. The problem here is that it is going to be difficult to agree on what this
support should constitute on each platform
I agree with you here, which is one reason why I like the logical types. It's
valuable to have standard representations that aren't necessarily tied to the
object model. But what I'm trying to get at is whether your IPC use case for
the string representations could be solved another way. I know it's easier to
debug with ISO-8601 strings rather than ints, but it seems like this probably
doesn't apply to bytes on the wire because those the format is (usually) binary
for everything else.
Maybe I'm wrong about this, but it seems like using strings would probably be
most helpful in debugging the application. And if that's the case, we can
provide a few simple tools for working with these types rather than changing
the representation to avoid the conversion. What about adding a set of helpers
that works like this:
{code:java}
String date = Iso8601.dateAsString( record.get("date") );
String time = Iso8601.timeAsString( record.get("time") );
String timestamp = Iso8601.timestampAsString( record.get("timestamp") );
{code}
Would that help you debug these applications without needing a different
representation? Or do you need the wire protocol to include the date/time
string for debugging? If so, why is it necessary to treat date/time differently
than other types that are binary-encoded?
> 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)
