[jira] [Resolved] (FLINK-6653) Avoid directly serializing AWS's Shard class in Kinesis consumer's checkpoints

["Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org>]

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

Tzu-Li (Gordon) Tai resolved FLINK-6653.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0
                   1.3.0

Thanks for the contribution Tony!

Fixed for master via 2597e7e1803da66190ff545e705a6a4e6a6f76a2.
Fixed for 1.3 via 7fe4df3361136755e0ca9c5647b178fdb65053f2.

> Avoid directly serializing AWS's Shard class in Kinesis consumer's checkpoints
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-6653
>                 URL: https://issues.apache.org/jira/browse/FLINK-6653
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kinesis Connector
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Wei-Che Wei
>             Fix For: 1.3.0, 1.4.0
>
>
> Currently, the Kinesis consumer's checkpoints directly serialize AWS's {{Shard}} instances in checkpoints. This makes bumping AWS library versions hard, since any change to the {{Shard}} class by AWS will break checkpoint compatibility.
> We should either have custom serialization for {{KinesisStreamShard}}, or disintegrate the information in {{Shard}}. Ideally, it would be best to make {{KinesisStreamShard}} and {{SequenceNumber}} to be non-serializable, hence avoiding Java serialization in the checkpoints.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)