[
https://issues.apache.org/jira/browse/BEAM-9863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17097489#comment-17097489
]
Brian Hulette commented on BEAM-9863:
-------------------------------------
I could maybe take this if we identify an appropriate fix.
Rather than registering this timestamp conversion on the singleton instance of
GenericData and SpecificData, do we just need to create our own instances for
use within AvroUtils?
What about avro objects that come from user code? Would we then need to
register the timestamp conversion on them, or find some way to handle the
possibility that they don't return joda time?
> AvroUtils is converting incorrectly LogicalType Timestamps from long into
> Joda DateTimes
> ----------------------------------------------------------------------------------------
>
> Key: BEAM-9863
> URL: https://issues.apache.org/jira/browse/BEAM-9863
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Affects Versions: 2.15.0, 2.16.0, 2.17.0, 2.18.0, 2.19.0, 2.20.0, 2.21.0
> Reporter: Ismaël Mejía
> Assignee: Reuven Lax
> Priority: Major
>
> Copied from the mailing list report:
> I think the method AvroUtils.toBeamSchema has a not expected side effect.
> I found out that, if you invoke it and then you run a pipeline of
> GenericRecords containing a timestamp (l tried with logical-type
> timestamp-millis), Beam converts such timestamp from long to
> org.joda.time.DateTime. Even if you don't apply any transformation to the
> pipeline.
> Do you think it's a bug?
> More details on how to reproduce here:
> https://lists.apache.org/thread.html/r43fb2896e496b7493a962207eb3b95360abc30b9d091b26f110264d0%40%3Cuser.beam.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
