[
https://issues.apache.org/jira/browse/BEAM-13467?focusedWorklogId=696988&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-696988
]
ASF GitHub Bot logged work on BEAM-13467:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Dec/21 00:55
Start Date: 16/Dec/21 00:55
Worklog Time Spent: 10m
Work Description: laraschmidt commented on pull request #16249:
URL: https://github.com/apache/beam/pull/16249#issuecomment-995339602
Yup, I checked earlier that we do properly handle the field not being set.
Not sure how we missed this side of it.
--
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: 696988)
Remaining Estimate: 2h 20m (was: 2.5h)
Time Spent: 40m (was: 0.5h)
> Schema translation to proto doesn't handle null arguements
> ----------------------------------------------------------
>
> Key: BEAM-13467
> URL: https://issues.apache.org/jira/browse/BEAM-13467
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Lara Schmidt
> Assignee: Lara Schmidt
> Priority: P2
> Original Estimate: 3h
> Time Spent: 40m
> Remaining Estimate: 2h 20m
>
> Schema translation to proto gets a null exception when trying to handle a
> logical type with a null argument. The API documents that null is a valid
> type of argument if the logical type does not have an argument. Should be an
> easy fix.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
