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-9799) Generalize/unify state meta info
Date Thu, 12 Jul 2018 14:07:00 GMT

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

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

Github user StefanRRichter commented on a diff in the pull request:

    https://github.com/apache/flink/pull/6308#discussion_r202047581
  
    --- Diff: flink-runtime/src/main/java/org/apache/flink/runtime/state/KeyedBackendSerializationProxy.java
---
    @@ -98,8 +103,7 @@ public int getVersion() {
     
     	@Override
     	public int[] getCompatibleVersions() {
    -		// we are compatible with version 3 (Flink 1.3.x) and version 1 & 2 (Flink 1.2.x)
    -		return new int[] {VERSION, 3, 2, 1};
    +		return new int[]{VERSION, 4, 3, 2, 1};
    --- End diff --
    
    Both styles are ok and used in Flink, so I will stick to this.


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

Mime
View raw message