spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Armbrust (JIRA)" <>
Subject [jira] [Updated] (SPARK-17939) Spark-SQL Nullability: Optimizations vs. Enforcement Clarification
Date Wed, 03 May 2017 23:55:04 GMT


Michael Armbrust updated SPARK-17939:
    Target Version/s: 2.3.0  (was: 2.2.0)

> Spark-SQL Nullability: Optimizations vs. Enforcement Clarification
> ------------------------------------------------------------------
>                 Key: SPARK-17939
>                 URL:
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.0.0
>            Reporter: Aleksander Eskilson
>            Priority: Critical
> The notion of Nullability of of StructFields in DataFrames and Datasets creates some
confusion. As has been pointed out previously [1], Nullability is a hint to the Catalyst optimizer,
and is not meant to be a type-level enforcement. Allowing null fields can also help the reader
successfully parse certain types of more loosely-typed data, like JSON and CSV, where null
values are common, rather than just failing. 
> There's already been some movement to clarify the meaning of Nullable in the API, but
also some requests for a (perhaps completely separate) type-level implementation of Nullable
that can act as an enforcement contract.
> This bug is logged here to discuss and clarify this issue.
> [1] - [|]
> [2] -

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message