flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1178) Let ValueType and WritableType have preference over CaseClassType
Date Mon, 27 Oct 2014 13:59:33 GMT

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

ASF GitHub Bot commented on FLINK-1178:
---------------------------------------

Github user StephanEwen commented on the pull request:

    https://github.com/apache/incubator-flink/pull/162#issuecomment-60595832
  
    Good catch.
    
    Looks good to merge...


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

Mime
View raw message