[
https://issues.apache.org/jira/browse/BEAM-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964053#comment-15964053
]
Tobias Feldhaus commented on BEAM-1714:
---------------------------------------
{{TextIO.Read}} into {{ParDo(DoFn)}} that does some JSON Parsing and timestamp
magic, then writing it out. General logic looks comparable to
[https://gist.github.com/dhalperi/4bbd13021dd5f9998250cff99b155db6#file-dateshardedbigquerytables-java-L260]
- on each of my {{LogLine}} objects I am calling a self-written
{{toTableRow()}} method when writing it out. This method consists now of a lot
of if statements with null checks, that check every field before emitting it.
> Null Pointer Exception when outputting a TableRow with a Null value for a key
> -----------------------------------------------------------------------------
>
> Key: BEAM-1714
> URL: https://issues.apache.org/jira/browse/BEAM-1714
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-gcp
> Affects Versions: 0.5.0
> Reporter: Tobias Feldhaus
> Assignee: Mark Shalda
> Labels: newbie, starter
> Fix For: Not applicable
>
>
> When outputting a TableRow that has a Null value for a key, a Null Pointer
> Exception is thrown. In the Dataflow SDK (1.9) this case is handled by
> outputting NULL for that field.
> I would expect the same behavior from the Beam SDK - since otherwise there is
> always a lot of Null checking necessary in the user code. (Especially when
> there are nested fields.)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
