azagrebin opened a new pull request #6510: [State TTL] Swap serialization order in TTL value: first timestamp then user value URL: https://github.com/apache/flink/pull/6510 ## What is the purpose of the change The serialisation order in TTL value wrapper is changed in this PR. The user value and the timestamp are swapped: now the timestamp goes firstly and then the user value. ## Brief change log - change serializers order in TtlStateFactory.TtlSerializer - adjust the position of timstamp in byte state value transformer of TtlStateSnapshotTransformer - wrap state transformer for RocksDB map state to skip the first byte where the (non-)nullness of user value is encoded ## Verifying this change existing unit tests ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (yes) - The runtime per-record code paths (performance sensitive): (yes) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (not applicable)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
