You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Gidaspov (Jira)" <ji...@apache.org> on 2021/07/01 09:18:00 UTC

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

     [ https://issues.apache.org/jira/browse/IGNITE-14451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Gidaspov updated IGNITE-14451:
-------------------------------------
    Ignite Flags: Release Notes Required  (was: Docs Required,Release Notes Required)

> 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: 0.5h
>  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)