[IGNITE-16004] Preserve key order in InternalTableImpl#collectMultiRowsResponses

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Labels: ignite-3
• Epic Link: Ignite 3 transactions
• Assignee: Kirill Tkalenko
• Reporter: Alexey Scherbakov
• Reviewer: Ivan Bessonov
• Created: 26/Nov/21 06:44
• Updated: 04/Sep/24 16:19
• Resolved: 23/Jun/23 11:36

Description

After the IGNITE-15085 multi key methods return a List of values correponding to the passed keys order, where each position correponds to the result operation for a key with the same position in the arguments.

For example, getAll(1, 2, 3) will return A, null, C if a value for 2 doesn't exists.

collectMultiRowsResponses can break this ordering for multi partition requests.

Issue Links

• blocks: IGNITE-16022 Thin 3.0: Optimize multi-row responses using guaranteed order
• causes: IGNITE-19693 getAll does not preserve order and does not return nulls for missing keys
• is caused by: IGNITE-15085 Implement tx coordination
• is cloned by: IGNITE-20435 Preserve key order in batch opperations (deleteAll, deleteAllExact, insertAll)
• links to: GitHub Pull Request #503
• links to: GitHub Pull Request #2236