[
https://issues.apache.org/jira/browse/FLINK-9799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16541659#comment-16541659
]
ASF GitHub Bot commented on FLINK-9799:
---------------------------------------
Github user azagrebin commented on a diff in the pull request:
https://github.com/apache/flink/pull/6308#discussion_r201798531
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/state/OperatorBackendSerializationProxy.java
---
@@ -62,62 +67,62 @@ public int getVersion() {
@Override
public int[] getCompatibleVersions() {
- // we are compatible with version 3 (Flink 1.5.x), 2 (Flink
1.4.x, Flink 1.3.x) and version 1 (Flink 1.2.x)
--- End diff --
was this comment redundant?
> Generalize/unify state meta info
> --------------------------------
>
> Key: FLINK-9799
> URL: https://issues.apache.org/jira/browse/FLINK-9799
> Project: Flink
> Issue Type: Sub-task
> Components: State Backends, Checkpointing
> Affects Versions: 1.5.0
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Priority: Major
> Labels: pull-request-available
>
> Flink currently has a couple of classes that describe the meta data of state
> (e.g. for keyed state, operator state, broadcast state, ...) and they
> typically come with their own serialization proxy and backwards compatibility
> story. However, the differences between those meta data classes are very
> small, like different option flags and a different set of serializers. Before
> introducing yet another meta data for timers, we should unify them in a
> general state meta data class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
