You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:50:06 UTC

[jira] [Updated] (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:all-tabpanel ]

Kenneth Knowles updated BEAM-11323:
-----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> 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: P3
>              Labels: Clarified
>          Time Spent: 40m
>  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.20.1#820001)