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

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

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

    https://github.com/apache/flink/pull/6196#discussion_r198114853
  
    --- Diff: 
flink-core/src/main/java/org/apache/flink/api/common/typeutils/CompositeSerializer.java
 ---
    @@ -0,0 +1,204 @@
    +package org.apache.flink.api.common.typeutils;
    +
    +import org.apache.flink.api.java.tuple.Tuple2;
    +import org.apache.flink.core.memory.DataInputView;
    +import org.apache.flink.core.memory.DataOutputView;
    +import org.apache.flink.util.Preconditions;
    +
    +import java.io.IOException;
    +import java.util.ArrayList;
    +import java.util.List;
    +import java.util.stream.Collectors;
    +import java.util.stream.IntStream;
    +
    +/**
    + * Base class for composite serializers.
    + *
    + * <p>This class serializes a list of objects
    + *
    + * @param <T> type of custom serialized value
    + */
    +@SuppressWarnings("unchecked")
    +public abstract class CompositeSerializer<T> extends TypeSerializer<T> {
    --- End diff --
    
    You could simply have tests for all the new serializer by extending 
`SerializerTestBase`, which I would recommend to do to catch mistakes.


> Wrap state binder with TTL logic
> --------------------------------
>
>                 Key: FLINK-9513
>                 URL: https://issues.apache.org/jira/browse/FLINK-9513
>             Project: Flink
>          Issue Type: Sub-task
>          Components: State Backends, Checkpointing
>    Affects Versions: 1.6.0
>            Reporter: Andrey Zagrebin
>            Assignee: Andrey Zagrebin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.0
>
>
> The main idea is to wrap user state value with a class holding the value and 
> the expiration timestamp (maybe meta data in future) and use the new object 
> as a value in the existing implementations:
> {code:java}
> class TtlValue<V> {
>   V value;
>   long expirationTimestamp;
> }
> {code}
> The original state binder factory is wrapped with TtlStateBinder if TTL is 
> enabled:
> {code:java}
> state = ttlConfig.updateType == DISABLED ?
>  bind(binder) : bind(new TtlStateBinder(binder, timerService));
> {code}
> TtlStateBinder decorates the states produced by the original binder with TTL 
> logic wrappers and adds TtlValue serialisation logic:
> {code:java}
> TtlStateBinder {
>     StateBinder binder;
>     ProcessingTimeProvier timeProvider; // System.currentTimeMillis()
>     <V> TtlValueState<V> createValueState(valueDesc) {
>          serializer = new TtlValueSerializer(valueDesc.getSerializer);
>          ttlValueDesc = new ValueDesc(serializer, ...);
>          // or implement custom TypeInfo
>          originalStateWithTtl = binder.createValueState(valueDesc);
>          return new TtlValueState(originalStateWithTtl, timeProvider);
>     }
>       // List, Map, ...
> }
> {code}
> TTL serializer should add expiration timestamp



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to