You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2014/10/27 17:17:33 UTC

[jira] [Closed] (FLINK-1178) Let ValueType and WritableType have preference over CaseClassType

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

Till Rohrmann closed FLINK-1178.
--------------------------------
    Resolution: Fixed

Fixed in https://github.com/apache/incubator-flink/commit/f2b8650e3968daf695af832470083afbc8d161b3

> Let ValueType and WritableType have preference over CaseClassType
> -----------------------------------------------------------------
>
>                 Key: FLINK-1178
>                 URL: https://issues.apache.org/jira/browse/FLINK-1178
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Till Rohrmann
>
> It is currently not possible to define a case class in the Scala API with custom serialization logic. A CaseClassSerializer with the respective field serializers will be generated for each case class. This approach fails, if the case class contains a field which is not serializable. So currently, one has to provide a Wrapper inheriting from Value or Writable for this field in order to circumvent this problem. A more convenient solution would be to let the case class implement the Value or Writable interface and provide a serialization method for the whole case class. For that to work, case class which implement one of the afore mentioned interfaces have to be treated as those types by the TypeAnalyzer.



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