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

Yury Gerzhedovich updated IGNITE-11125:
---------------------------------------
    Description: 
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

 

  was:
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

 


> 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)

Reply via email to