[jira] [Resolved] (SPARK-12371) Make sure non-nullable arguments of NewInstance don't receive null input data

["Cheng Lian (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-12371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cheng Lian resolved SPARK-12371.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Issue resolved by pull request 10331
[https://github.com/apache/spark/pull/10331]

> Make sure non-nullable arguments of NewInstance don't receive null input data
> -----------------------------------------------------------------------------
>
>                 Key: SPARK-12371
>                 URL: https://issues.apache.org/jira/browse/SPARK-12371
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 1.6.0, 2.0.0
>            Reporter: Cheng Lian
>            Assignee: Apache Spark
>             Fix For: 2.0.0
>
>
> When extracting objects from underlying rows using a Dataset, it's possible that a null is fed to a non-nullable constructor argument of the user level class.  It would be nice to add runtime check for this case and provide better error messages to ask the users to use {{Option}} or other nullable types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org