spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jungtaek Lim (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-26991) Investigate difference of `returnNullable` between ScalaReflection.deserializerFor and JavaTypeInference.deserializerFor
Date Fri, 01 Mar 2019 09:10:00 GMT

    [ https://issues.apache.org/jira/browse/SPARK-26991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781487#comment-16781487
] 

Jungtaek Lim commented on SPARK-26991:
--------------------------------------

This issue could be extended to investigate the difference between ScalaReflection and JavaTypeInference,
as we have found another case as well.

[https://github.com/apache/spark/pull/23908#discussion_r261511454]

 

> Investigate difference of `returnNullable` between ScalaReflection.deserializerFor and
JavaTypeInference.deserializerFor
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-26991
>                 URL: https://issues.apache.org/jira/browse/SPARK-26991
>             Project: Spark
>          Issue Type: Task
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Jungtaek Lim
>            Priority: Major
>
> This issue tracks the effort on investigation on difference between ScalaReflection.deserializerFor
and JavaTypeInference.deserializerFor, especially the reason why Java side uses `returnNullable
= true` whereas `returnNullable = false`.
> The origin discussion is linked here:
> https://github.com/apache/spark/pull/23854#discussion_r260117702



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message