You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/01/23 17:14:03 UTC
[jira] [Commented] (BEAM-11323) Date type mapping from AVRO to Beam
Schema produces invalid schema when used with Beam SQL
[ https://issues.apache.org/jira/browse/BEAM-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270705#comment-17270705 ]
Beam JIRA Bot commented on BEAM-11323:
--------------------------------------
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.
> Date type mapping from AVRO to Beam Schema produces invalid schema when used with Beam SQL
> ------------------------------------------------------------------------------------------
>
> Key: BEAM-11323
> URL: https://issues.apache.org/jira/browse/BEAM-11323
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Affects Versions: 2.25.0
> Reporter: Steven van Rossum
> Priority: P2
> Labels: Clarified, stale-P2
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The date type mapping in AvroUtils (introduced in https://github.com/apache/beam/pull/9152) produces DATETIME fields for AVRO fields with logical type date. Beam SQL expects LOGICAL_TYPE/Date for DATE fields, which was introduced after the AvroUtils mapping was made.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)