[
https://issues.apache.org/jira/browse/IGNITE-19914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742371#comment-17742371
]
Pavel Tupitsyn commented on IGNITE-19914:
-----------------------------------------
Merged to main: 7e1e0cf74c741a8d9c7c9e678535a4ca04fb8dc9
> .NET: Thin 3.0: Colocation column order is not preserved
> --------------------------------------------------------
>
> Key: IGNITE-19914
> URL: https://issues.apache.org/jira/browse/IGNITE-19914
> Project: Ignite
> Issue Type: Bug
> Components: thin client
> Affects Versions: 3.0.0-beta1
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [ClientTableCommon#writeSchema|https://github.com/apache/ignite-3/blob/317aca963ed9c87e14dd6eebd3284408fb550c8c/modules/client-handler/src/main/java/org/apache/ignite/client/handler/requests/table/ClientTableCommon.java#L75]
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
