[
https://issues.apache.org/jira/browse/FLINK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595827#comment-14595827
]
ASF GitHub Bot commented on FLINK-2194:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/814#issuecomment-114080543
I am unsure of where this leads us. The purpose of `Writable` is to make
sure that we can use the Writable's custom serialization. If the type
`Writable` itself is now treated as a generic type, it is serialized with Kryo
and that voids the assumption that it uses its own serialization code.
What is the reason for doing it this way? Throwing an error that "raw"
Writables are not supported would help them understand the issues easier...
> Type extractor does not support Writable type
> ---------------------------------------------
>
> Key: FLINK-2194
> URL: https://issues.apache.org/jira/browse/FLINK-2194
> Project: Flink
> Issue Type: Bug
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
>
> The type extractor supports sub types of {{Writable}} but not {{Writable}}
> itself. The reason is that it wants to create a {{WritableTypeInfo}} which is
> not possible for the interface {{Writable}}, though. A solution would be to
> treat the {{Writable}} interface like a generic type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
