[
https://issues.apache.org/jira/browse/IGNITE-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209150#comment-16209150
]
Vladimir Ozerov commented on IGNITE-6662:
-----------------------------------------
Test run: https://ci.ignite.apache.org/viewQueued.html?itemId=897354
> SQL: affinity key column is resolved incorrectly in GridH2Table
> ---------------------------------------------------------------
>
> Key: IGNITE-6662
> URL: https://issues.apache.org/jira/browse/IGNITE-6662
> Project: Ignite
> Issue Type: Task
> Security Level: Public(Viewable by anyone)
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 2.3
>
>
> Reproducer:
> 1) Start empty node;
> 2) Execute {{CREATE TABLE Department (id LONG PRIMARY KEY, name VARCHAR)}}
> 3) Observe in debugger how additional "AFFINITY KEY" index is created for the
> table.
> Root cause: we do not check whether resolved affinity key column is
> effectively an alias to the {{_KEY}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
