You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Andrey Zagrebin (JIRA)" <ji...@apache.org> on 2018/08/07 12:49:00 UTC

[jira] [Created] (FLINK-10095) Change the serialisation order in TTL value wrapper

Andrey Zagrebin created FLINK-10095:
---------------------------------------

             Summary: Change the serialisation order in TTL value wrapper
                 Key: FLINK-10095
                 URL: https://issues.apache.org/jira/browse/FLINK-10095
             Project: Flink
          Issue Type: Improvement
          Components: State Backends, Checkpointing
            Reporter: Andrey Zagrebin
            Assignee: Andrey Zagrebin


The first implementation of TTL value wrapper has the following serialisation order: first user value, then last modification timestamp.

This was planned for potential optimisation where we could peek at the last bytes of last element of list to check whether the whole list expired or not. After careful consideration, it is not the frequent case and the list is handled per entry mostly.

Having the fixed part (the timestamp) at the beginning looks more promising in future as we can skip looking into the rest of bytes if needed when working directly with serialised value.

This issue suggests to change the serialisation order.



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