[
https://issues.apache.org/jira/browse/FLINK-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177078#comment-14177078
]
ASF GitHub Bot commented on FLINK-1178:
---------------------------------------
GitHub user tillrohrmann opened a pull request:
https://github.com/apache/incubator-flink/pull/162
[FLINK-1178] Changed type preference to ValueType, WritableType,
CaseClassType
Case class which implement the Value or Writable interface are now treated
as one of those types. This allows to add custom serialization logic to case
classes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/incubator-flink FLINK-1178
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-flink/pull/162.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #162
----
commit 9a3a7b894f1420879a66737f3a4f686e80de1c77
Author: Till Rohrmann <trohrm...@apache.org>
Date: 2014-10-20T16:28:21Z
Changed type preference to ValueType, WritableType, CaseClassType
----
> 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)
