You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2016/11/17 09:34:59 UTC

[jira] [Commented] (SPARK-18122) Fallback to Kryo for unknown classes in ExpressionEncoder

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

Apache Spark commented on SPARK-18122:
--------------------------------------

User 'windpiger' has created a pull request for this issue:
https://github.com/apache/spark/pull/15918

> Fallback to Kryo for unknown classes in ExpressionEncoder
> ---------------------------------------------------------
>
>                 Key: SPARK-18122
>                 URL: https://issues.apache.org/jira/browse/SPARK-18122
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.0.1
>            Reporter: Michael Armbrust
>            Priority: Critical
>
> In Spark 2.0 we fail to generate an encoder if any of the fields of the class are not of a supported type.  One example is {{Option\[Set\[Int\]\]}}, but there are many more.  We should give the user the option to fall back on opaque kryo serialization in these cases for subtrees of the encoder, rather than failing.



--
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