[ https://issues.apache.org/jira/browse/IGNITE-14869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maksim Timonin updated IGNITE-14869: ------------------------------------ Description: Reproducer from user list: [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashed-with-CorruptedTreeException-tt36173.html] Reason is: # User specified table with fields order (viewId, status); # User specified primary key with different order (status, viewId); # Index created with (status, viewId); # After restart cluster index builds with (viewId, status) due to different handling of PK fields after recovery (H2TableDescriptor) was: Reproducer from user list: http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashed-with-CorruptedTreeException-tt36173.html > Wrong key fields order for recovery index. Leads to CorruptedTreeException > -------------------------------------------------------------------------- > > Key: IGNITE-14869 > URL: https://issues.apache.org/jira/browse/IGNITE-14869 > Project: Ignite > Issue Type: New Feature > Reporter: Maksim Timonin > Assignee: Maksim Timonin > Priority: Major > > Reproducer from user list: > [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashed-with-CorruptedTreeException-tt36173.html] > > Reason is: > # User specified table with fields order (viewId, status); > # User specified primary key with different order (status, viewId); > # Index created with (status, viewId); > # After restart cluster index builds with (viewId, status) due to different > handling of PK fields after recovery (H2TableDescriptor) -- This message was sent by Atlassian Jira (v8.3.4#803005)