[
https://issues.apache.org/jira/browse/SPARK-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15699681#comment-15699681
]
koert kuipers commented on SPARK-18122:
---------------------------------------
[~sowen] why won'f fix? what changed
[~marmbrus] thought this as a good idea, see conversation here:
http://apache-spark-developers-list.1001551.n3.nabble.com/getting-encoder-implicits-to-be-more-accurate-td19561.html
> 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: [email protected]
For additional commands, e-mail: [email protected]
