[IGNITE-20609] Move last commit timestamp into BinaryRowMessage

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Vladislav Pyatkov
• Reporter: Kirill Sizov
• Reviewer: Kirill Sizov
• Created: 10/Oct/23 10:44
• Updated: 04/Sep/24 16:10
• Resolved: 31/Oct/23 14:27

Description

Motivation
UpdateAllCommand now has two maps:
Map<UUID, BinaryRowMessage> rowsToUpdate()
and
Map<UUID, Long> lastCommitTimestampsLong() and the keys in both maps denote to the same set of rows.

We can get rid of the duplication to reduce the size of the message if instead of two maps we had a single one where the new value class would contain both BinaryRowMessage and last row commit timestamp.

Implementation details

1. BinaryRowMessage is used in many other places, perhaps we could subsclass it instead of adding more data to the message class itself.
2. While implementing this task we need to be careful since currently a null BinaryRowMessage is a valid case when we perform DELETE. If we subclass BinaryRowMessage, we should also change the nullability of the row.

Issue Links

• is caused by: IGNITE-20445 Clean up write intents for RW transaction on replication group nodes
• links to: GitHub Pull Request #2749