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

2021-04-05 Thread Konstantin Orlov (Jira) 


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

Konstantin Orlov commented on IGNITE-14451:
---

[~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)

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

2021-04-05 Thread Ignite TC Bot (Jira) 


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

Ignite TC Bot commented on IGNITE-14451:


{panel:title=Branch: [pull/8951/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8951/head] Base: [master] : New Tests 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=5948045]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite: 
BasicIndexMultinodeTest.testCorrectPkFieldsSequenceAfterRestart - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite: 
BasicIndexTest.testCorrectPkFieldsSequenceAfterRestart - PASSED{color}

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5948066buildTypeId=IgniteTests24Java8_RunAll]

> 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: 10m
>  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)

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

2021-04-05 Thread Taras Ledkov (Jira) 


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

Taras Ledkov commented on IGNITE-14451:
---

[~korlov], please review the patch.

> 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: 10m
>  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)