ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Pavlukhin (Jira)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-11125) Use alternative column instead of special _key for indexes.
Date Mon, 30 Sep 2019 12:23:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-11125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ivan Pavlukhin reassigned IGNITE-11125:
---------------------------------------

    Assignee: Ivan Pavlukhin

> 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: Ivan Pavlukhin
>            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
>  
>  
> The task may be better to do together with [IGNITE-11250|https://issues.apache.org/jira/browse/IGNITE-11250],
due to, seems, both of them required compatibility changes. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message