[
https://issues.apache.org/jira/browse/AVRO-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090614#comment-14090614
]
Dmitry Kovalev commented on AVRO-739:
-------------------------------------
bq. is this something that we could realistically accomplish with better
support for logical types in the data models? If, for example, we added the
conversion to a Calendar or a Date to deserialization rather than returning
integers or longs, would that meet your use case?
The problem here is that it is going to be difficult to agree on what this
support should constitute on each platform. For example, I don't care about
either Date or Calendar (or .NET DateTime for that matter) - none of these can
inambiguously represent all the different kinds of date/time data that I need
to communicate. JodaTime/ NodaTime provide all the types I need, but people
would probably not be happy to add these libraries as firm dependencies in Avro
codebase. Newer versions of Java and .NET are going to try and address this
problem by embracing core concepts from those libraries, but currently on these
platforms there are just no standard types which we could safely translate to.
So at the moment the best that could be done is to provide on each platform a
framework for plugging in logical type "implementations", including the codegen
for specific, and a means for the users to specify which one to use. Then on
top of this core framework there could be "contributed" implementations for
most popular types.
> 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)
