[jira] [Comment Edited] (IGNITE-14451) PK becomes corrupted after node restart

["Konstantin Orlov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-14451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314792#comment-17314792 ] 

Konstantin Orlov edited comment on IGNITE-14451 at 4/5/21, 11:12 AM:
---------------------------------------------------------------------

[~tledkov-gridgain], LGTM in general, but i left a minor remark. Please see PR.


was (Author: korlov):
[~tledkov-gridgain], in general LGTM, but if left a minor remark. Please see PR.

> PK becomes corrupted after node restart
> ---------------------------------------
>
>                 Key: IGNITE-14451
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14451
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Taras Ledkov
>            Assignee: Taras Ledkov
>            Priority: Major
>             Fix For: 2.11
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> PK index tree becomes corrupted after node restart in case it was created through SQL API and it's fields order differs from the one in field list. For example:
> CREATE TABLE t (id1 INTEGER, id2 INTEGER, val VARCHAR, CONSTRAINT PK PRIMARY KEY (id2, id1)) - this won't survive restart.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)