[IGNITE-19914] .NET: Thin 3.0: Colocation column order is not preserved

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta1
• Fix Version/s: 3.0
• Component/s: thin client
• Labels: ignite-3
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Reviewer: Igor Sapego
• Created: 05/Jul/23 07:14
• Updated: 04/Sep/24 16:10
• Resolved: 12/Jul/23 10:46

Description

ClientTableCommon#writeSchema does not preserve the order of colocation columns. It assumes that key column order is the same as colocation column order, which is not always true.

• Fix writeSchema somehow to specify the order of colocation columns (maybe send their indices as a separate array)
• Fix clients (.NET, Java, C++) accordingly

Issue Links

• is a clone of: IGNITE-19756 Thin 3.0: Colocation column order is not preserved
• is blocked by: IGNITE-19935 Allow combining individual colocation hashes
• relates to: IGNITE-19970 Java thin 3.0: Combine hashing with serialization
• links to: GitHub Pull Request #2308