[
https://issues.apache.org/jira/browse/BEAM-5884?focusedWorklogId=162711&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-162711
]
ASF GitHub Bot logged work on BEAM-5884:
----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Nov/18 19:27
Start Date: 05/Nov/18 19:27
Worklog Time Spent: 10m
Work Description: kanterov commented on issue #6861: [BEAM-5884] support
null values in Array and Map.
URL: https://github.com/apache/beam/pull/6861#issuecomment-436003580
> We should do this regardless, but I'm curious what the SQL standard and
other engines support.
@kennknowles Out of my head, limitations in Spark SQL, it doesn't support
types like:
`Map<Optional<?>, ?>`
`Record(field: Optional<Record(field: Optional<?>)>)`
As I remember, the reason for records is they are stored in the flattened
form, that requires expressing `Optional<Optional<?>>` that doesn't work
because a boolean flag is used.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 162711)
Time Spent: 3h 20m (was: 3h 10m)
> 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: 3h 20m
> 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)
