You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2015/11/18 09:10:10 UTC

[jira] [Resolved] (SPARK-11802) Kryo-based encoder for opaque types

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

Reynold Xin resolved SPARK-11802.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0

> Kryo-based encoder for opaque types
> -----------------------------------
>
>                 Key: SPARK-11802
>                 URL: https://issues.apache.org/jira/browse/SPARK-11802
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>            Reporter: Reynold Xin
>            Assignee: Reynold Xin
>             Fix For: 1.6.0
>
>
> Users of Spark SQL Datasets should be able to use objects that we don't understand (i.e. today not primitives or case classes) in Spark Datasets.  To allow this, lets add a default encoder that uses kryo to store the class as bytes and presents it as a single field {{value}}.
> For now, lets require the user to explicitly pass the encoder, but as a bonus we can explore the option to use this as a fallback automatically.
> This encoder should be usable in:
>  - as
>  - map/flatMap, etc
>  - Custom Aggregators
>  - Scala/Java



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