[
https://issues.apache.org/jira/browse/FLINK-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066234#comment-14066234
]
ASF GitHub Bot commented on FLINK-610:
--------------------------------------
Github user tillrohrmann commented on the pull request:
https://github.com/apache/incubator-flink/pull/74#issuecomment-49416463
The underlying problem is that Flink can use different serializers for
serialized objects in one stream. Thus, it is not possible to use the Kryo
serializer all the time. If that weren't the case, it would not matter whether
Kryo already read some data into its buffer belonging to the next object.
If we have a memory abstraction instead of a stream, as proposed in
[FLINK-987](https://issues.apache.org/jira/browse/FLINK-987), which allows to
seek the current pointer, we should be able to virtually write data back which
has been read from a different object. However, that would require that we can
seek backwards over memory segment borders.
> Replace Avro serialization by Kryo
> -----------------------------------
>
> Key: FLINK-610
> URL: https://issues.apache.org/jira/browse/FLINK-610
> Project: Flink
> Issue Type: Bug
> Components: Java API
> Reporter: GitHub Import
> Assignee: Till Rohrmann
> Priority: Critical
> Labels: github-import
> Fix For: pre-apache
>
>
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/stratosphere/stratosphere/issues/610
> Created by: [rmetzger|https://github.com/rmetzger]
> Labels: java api,
> Milestone: Release 0.6 (unplanned)
> Created at: Tue Mar 18 17:29:28 CET 2014
> State: open
--
This message was sent by Atlassian JIRA
(v6.2#6252)
