[
https://issues.apache.org/jira/browse/BEAM-5884?focusedWorklogId=159750&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-159750
]
ASF GitHub Bot logged work on BEAM-5884:
----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Oct/18 19:57
Start Date: 28/Oct/18 19:57
Worklog Time Spent: 10m
Work Description: reuvenlax commented on issue #6861: [BEAM-5884] support
null values in Array and Map.
URL: https://github.com/apache/beam/pull/6861#issuecomment-433736172
What should the default for list entries be? Nullable or not nullable?
On Sun, Oct 28, 2018 at 12:55 PM Kenn Knowles <notificati...@github.com>
wrote:
> Use case: if a field is missing from an input data set, i.e. unknown, that
> is a different situation that a known empty array. Every data type needs to
> have the ability to be nullable.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/beam/pull/6861#issuecomment-433736007>, or mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AUGE1ShWNw8Cfcl1u8W9LXKRQwsfM1Ygks5upguagaJpZM4X9yY->
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 159750)
Time Spent: 1.5h (was: 1h 20m)
> Allow nested types have null value.
> -----------------------------------
>
> Key: BEAM-5884
> URL: https://issues.apache.org/jira/browse/BEAM-5884
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql
> Reporter: Rui Wang
> Assignee: Rui Wang
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> We could allow arbitrary combination of nested types have null value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
