[
https://issues.apache.org/jira/browse/BEAM-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123331#comment-17123331
]
Beam JIRA Bot commented on BEAM-4438:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> AvroCoder - Support Logical Types
> ---------------------------------
>
> Key: BEAM-4438
> URL: https://issues.apache.org/jira/browse/BEAM-4438
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Nalseez Duke
> Priority: P2
> Labels: stale-P2
>
> Context (from ASF Slack, BEAM channel):
> {code:java}
> Hey all!
> So I've been working with the BEAM 2.4.0 Java SDK, and I am trying to see if
> Avro Logical Types
> (https://avro.apache.org/docs/1.8.2/spec.html#Logical+Types) are supported
> within the AvroCoder.
> From what I'm seeing it doesn't seem to be the case, though maybe I'm missing
> something. Does it make sense to allow for a user to supply a set of
> Conversion(s) to be used within the ReflectData in the AvroCoder?
> {code}
> Potentially relevant Apache Avro Bug:
> https://issues.apache.org/jira/browse/AVRO-1891
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
