[jira] [Updated] (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:all-tabpanel ] Maxim Muzafarov updated IGNITE-11125: - Fix Version/s: (was: 2.8) > 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 >Priority: Major > 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)
[jira] [Updated] (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: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 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. 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 > > > 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 (v7.6.3#76005)
[jira] [Updated] (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: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)
[jira] [Updated] (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: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 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 CACHE_SQL (ID INT PRIMARY KEY, MY_VAL VARCHAR) will be used index with two columns ID and _KEY. > 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)
