[
https://issues.apache.org/jira/browse/IGNITE-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209149#comment-16209149
]
ASF GitHub Bot commented on IGNITE-6662:
----------------------------------------
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2875
IGNITE-6662
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6662
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2875.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2875
----
commit cf6b28e6e0676db0f8637358581462002401e3ac
Author: devozerov <voze...@gridgain.com>
Date: 2017-10-18T10:56:22Z
IGNITE-6662
----
> 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)
