[
https://issues.apache.org/jira/browse/FLINK-10095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Richter closed FLINK-10095.
----------------------------------
Resolution: Implemented
Fix Version/s: 1.6.0
Merged in:
master: b535fab
release-1.6: f45f04b
> 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
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> 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)
