[ 
https://issues.apache.org/jira/browse/BEAM-11323?focusedWorklogId=725925&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-725925
 ]

ASF GitHub Bot logged work on BEAM-11323:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Feb/22 02:28
            Start Date: 14/Feb/22 02:28
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #13408:
URL: https://github.com/apache/beam/pull/13408#issuecomment-1037214743


   This pull request has been closed due to lack of activity. If you think that 
is incorrect, or the pull request requires review, you can revive the PR at any 
time.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 725925)
    Time Spent: 1h 20m  (was: 1h 10m)

> 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: 1h 20m
>  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)

Reply via email to