You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/01/29 20:31:00 UTC
[jira] [Commented] (IGNITE-11125) Use alternative column instead of
special _key for indexes.
[ https://issues.apache.org/jira/browse/IGNITE-11125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755369#comment-16755369 ]
Ignite TC Bot commented on IGNITE-11125:
----------------------------------------
{panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2942240&buildTypeId=IgniteTests24Java8_RunAll]
> Use alternative column instead of special _key for indexes.
> -----------------------------------------------------------
>
> Key: IGNITE-11125
> URL: https://issues.apache.org/jira/browse/IGNITE-11125
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Yury Gerzhedovich
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently we can have the same columns for sorted inline indexes twice because in part cases use alternative columns for another case special column _key. To avoid duplicate the same columns need to use alternative columns (real columns) always.
>
> For example for
> CREATE TABLE PUBLIC.DFLT_CACHE (ID1 INT, ID2 INT, MY_VAL VARCHAR, PRIMARY KEY (ID1 DESC, ID2))
> CREATE INDEX IDX_1 ON PUBLIC.DFLT_CACHE(ID2 DESC, ID1, MY_VAL DESC)
>
> will be use the follow columns ID2 DESC, ID1, MY_VAL DESC, _KEY instead of ID2 DESC, ID1, MY_VAL DESC
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)