[jira] [Commented] (IGNITE-13376) Primary index can be created with fields sequence differ from declared.

2020-10-14 Thread Aleksey Plekhanov (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17213642#comment-17213642
 ] 

Aleksey Plekhanov commented on IGNITE-13376:


Cherry-picked to 2.9
[~tledkov-gridgain], please be careful next time resolving ticket (set correct 
"fix version" or note about the ticket on dev-list if the ticket should be 
included into release after the code freeze stage)

> Primary index can be created with fields sequence differ from declared.
> ---
>
> Key: IGNITE-13376
> URL: https://issues.apache.org/jira/browse/IGNITE-13376
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7.6, 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce: 
> Execute the following DDL (create table + create index):
> {noformat}
> CREATE TABLE IF NOT EXISTS Workspace (
> id UUID NOT NULL,
> accountId UUID NOT NULL,
> jsonModel VARCHAR,
> PRIMARY KEY (accountId, id)
>   ) WITH 
> "template=partitioned,atomicity=transactional,key_type=org.gridgain.gmc.dto.workspace.WorkspaceKey,value_type=workspace.Workspace,cache_name=WorkspaceCache";
> CREATE INDEX IF NOT EXISTS workspace_id_account_id_idx ON Workspace (id, 
> accountId);
> {noformat}
> On node start got the following warning:
> {noformat}
> Index with the given set or subset of columns already exists (consider 
> dropping either new or existing index) [cacheName=WorkspaceCache, 
> schemaName=PUBLIC, tableName=WORKSPACE, 
> newIndexName=WORKSPACE_ID_ACCOUNT_ID_IDX, existingIndexName=_key_PK, 
> existingIndexColumns=[ID, ACCOUNTID]]
> {noformat}
> But PK and index have different order!



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

[jira] [Commented] (IGNITE-13376) Primary index can be created with fields sequence differ from declared.

2020-08-25 Thread Stanilovsky Evgeny (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183965#comment-17183965
 ] 

Stanilovsky Evgeny commented on IGNITE-13376:
-

[~tledkov-gridgain] seems all ok

> Primary index can be created with fields sequence differ from declared.
> ---
>
> Key: IGNITE-13376
> URL: https://issues.apache.org/jira/browse/IGNITE-13376
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7.6, 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce: 
> Execute the following DDL (create table + create index):
> {noformat}
> CREATE TABLE IF NOT EXISTS Workspace (
> id UUID NOT NULL,
> accountId UUID NOT NULL,
> jsonModel VARCHAR,
> PRIMARY KEY (accountId, id)
>   ) WITH 
> "template=partitioned,atomicity=transactional,key_type=org.gridgain.gmc.dto.workspace.WorkspaceKey,value_type=workspace.Workspace,cache_name=WorkspaceCache";
> CREATE INDEX IF NOT EXISTS workspace_id_account_id_idx ON Workspace (id, 
> accountId);
> {noformat}
> On node start got the following warning:
> {noformat}
> Index with the given set or subset of columns already exists (consider 
> dropping either new or existing index) [cacheName=WorkspaceCache, 
> schemaName=PUBLIC, tableName=WORKSPACE, 
> newIndexName=WORKSPACE_ID_ACCOUNT_ID_IDX, existingIndexName=_key_PK, 
> existingIndexColumns=[ID, ACCOUNTID]]
> {noformat}
> But PK and index have different order!



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

[jira] [Commented] (IGNITE-13376) Primary index can be created with fields sequence differ from declared.

2020-08-25 Thread Ignite TC Bot (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183960#comment-17183960
 ] 

Ignite TC Bot commented on IGNITE-13376:


{panel:title=Branch: [pull/8172/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8172/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *~[Excluded] - Run :: IntelliJ IDEA Inspections* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5564415buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]

> Primary index can be created with fields sequence differ from declared.
> ---
>
> Key: IGNITE-13376
> URL: https://issues.apache.org/jira/browse/IGNITE-13376
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7.6, 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce: 
> Execute the following DDL (create table + create index):
> {noformat}
> CREATE TABLE IF NOT EXISTS Workspace (
> id UUID NOT NULL,
> accountId UUID NOT NULL,
> jsonModel VARCHAR,
> PRIMARY KEY (accountId, id)
>   ) WITH 
> "template=partitioned,atomicity=transactional,key_type=org.gridgain.gmc.dto.workspace.WorkspaceKey,value_type=workspace.Workspace,cache_name=WorkspaceCache";
> CREATE INDEX IF NOT EXISTS workspace_id_account_id_idx ON Workspace (id, 
> accountId);
> {noformat}
> On node start got the following warning:
> {noformat}
> Index with the given set or subset of columns already exists (consider 
> dropping either new or existing index) [cacheName=WorkspaceCache, 
> schemaName=PUBLIC, tableName=WORKSPACE, 
> newIndexName=WORKSPACE_ID_ACCOUNT_ID_IDX, existingIndexName=_key_PK, 
> existingIndexColumns=[ID, ACCOUNTID]]
> {noformat}
> But PK and index have different order!



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

[jira] [Commented] (IGNITE-13376) Primary index can be created with fields sequence differ from declared.

2020-08-25 Thread Stanilovsky Evgeny (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183952#comment-17183952
 ] 

Stanilovsky Evgeny commented on IGNITE-13376:
-

thanks ! TC in progress.

> Primary index can be created with fields sequence differ from declared.
> ---
>
> Key: IGNITE-13376
> URL: https://issues.apache.org/jira/browse/IGNITE-13376
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7.6, 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce: 
> Execute the following DDL (create table + create index):
> {noformat}
> CREATE TABLE IF NOT EXISTS Workspace (
> id UUID NOT NULL,
> accountId UUID NOT NULL,
> jsonModel VARCHAR,
> PRIMARY KEY (accountId, id)
>   ) WITH 
> "template=partitioned,atomicity=transactional,key_type=org.gridgain.gmc.dto.workspace.WorkspaceKey,value_type=workspace.Workspace,cache_name=WorkspaceCache";
> CREATE INDEX IF NOT EXISTS workspace_id_account_id_idx ON Workspace (id, 
> accountId);
> {noformat}
> On node start got the following warning:
> {noformat}
> Index with the given set or subset of columns already exists (consider 
> dropping either new or existing index) [cacheName=WorkspaceCache, 
> schemaName=PUBLIC, tableName=WORKSPACE, 
> newIndexName=WORKSPACE_ID_ACCOUNT_ID_IDX, existingIndexName=_key_PK, 
> existingIndexColumns=[ID, ACCOUNTID]]
> {noformat}
> But PK and index have different order!



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

[jira] [Commented] (IGNITE-13376) Primary index can be created with fields sequence differ from declared.

2020-08-25 Thread Taras Ledkov (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183923#comment-17183923
 ] 

Taras Ledkov commented on IGNITE-13376:
---

[~zstan], the patch is OK with me. Please fix typos and codestyle:
- BasicIndexTest#testCorrectPkFldsSequence - fix name according with 
[guideline|https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Abbreviations];
- GridQueryTypeDescriptor#primaryKeyFields(): typo at the javadoc;
- IgniteDiscoverySpi#SRV_NODES - [javadoc 
style|org.apache.ignite.internal.managers.discovery.IgniteDiscoverySpi#SRV_NODES].


> Primary index can be created with fields sequence differ from declared.
> ---
>
> Key: IGNITE-13376
> URL: https://issues.apache.org/jira/browse/IGNITE-13376
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7.6, 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce: 
> Execute the following DDL (create table + create index):
> {noformat}
> CREATE TABLE IF NOT EXISTS Workspace (
> id UUID NOT NULL,
> accountId UUID NOT NULL,
> jsonModel VARCHAR,
> PRIMARY KEY (accountId, id)
>   ) WITH 
> "template=partitioned,atomicity=transactional,key_type=org.gridgain.gmc.dto.workspace.WorkspaceKey,value_type=workspace.Workspace,cache_name=WorkspaceCache";
> CREATE INDEX IF NOT EXISTS workspace_id_account_id_idx ON Workspace (id, 
> accountId);
> {noformat}
> On node start got the following warning:
> {noformat}
> Index with the given set or subset of columns already exists (consider 
> dropping either new or existing index) [cacheName=WorkspaceCache, 
> schemaName=PUBLIC, tableName=WORKSPACE, 
> newIndexName=WORKSPACE_ID_ACCOUNT_ID_IDX, existingIndexName=_key_PK, 
> existingIndexColumns=[ID, ACCOUNTID]]
> {noformat}
> But PK and index have different order!



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

[jira] [Commented] (IGNITE-13376) Primary index can be created with fields sequence differ from declared.

2020-08-25 Thread Kirill Tkalenko (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183854#comment-17183854
 ] 

Kirill Tkalenko commented on IGNITE-13376:
--

[~tledkov-gridgain] Please make code review.

> Primary index can be created with fields sequence differ from declared.
> ---
>
> Key: IGNITE-13376
> URL: https://issues.apache.org/jira/browse/IGNITE-13376
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7.6, 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce: 
> Execute the following DDL (create table + create index):
> {noformat}
> CREATE TABLE IF NOT EXISTS Workspace (
> id UUID NOT NULL,
> accountId UUID NOT NULL,
> jsonModel VARCHAR,
> PRIMARY KEY (accountId, id)
>   ) WITH 
> "template=partitioned,atomicity=transactional,key_type=org.gridgain.gmc.dto.workspace.WorkspaceKey,value_type=workspace.Workspace,cache_name=WorkspaceCache";
> CREATE INDEX IF NOT EXISTS workspace_id_account_id_idx ON Workspace (id, 
> accountId);
> {noformat}
> On node start got the following warning:
> {noformat}
> Index with the given set or subset of columns already exists (consider 
> dropping either new or existing index) [cacheName=WorkspaceCache, 
> schemaName=PUBLIC, tableName=WORKSPACE, 
> newIndexName=WORKSPACE_ID_ACCOUNT_ID_IDX, existingIndexName=_key_PK, 
> existingIndexColumns=[ID, ACCOUNTID]]
> {noformat}
> But PK and index have different order!



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

[jira] [Commented] (IGNITE-13376) Primary index can be created with fields sequence differ from declared.

2020-08-21 Thread Stanilovsky Evgeny (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181816#comment-17181816
 ] 

Stanilovsky Evgeny commented on IGNITE-13376:
-

[~tledkov-gridgain] plz take a look ?

> Primary index can be created with fields sequence differ from declared.
> ---
>
> Key: IGNITE-13376
> URL: https://issues.apache.org/jira/browse/IGNITE-13376
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7.6, 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce: 
> Execute the following DDL (create table + create index):
> {noformat}
> CREATE TABLE IF NOT EXISTS Workspace (
> id UUID NOT NULL,
> accountId UUID NOT NULL,
> jsonModel VARCHAR,
> PRIMARY KEY (accountId, id)
>   ) WITH 
> "template=partitioned,atomicity=transactional,key_type=org.gridgain.gmc.dto.workspace.WorkspaceKey,value_type=workspace.Workspace,cache_name=WorkspaceCache";
> CREATE INDEX IF NOT EXISTS workspace_id_account_id_idx ON Workspace (id, 
> accountId);
> {noformat}
> On node start got the following warning:
> {noformat}
> Index with the given set or subset of columns already exists (consider 
> dropping either new or existing index) [cacheName=WorkspaceCache, 
> schemaName=PUBLIC, tableName=WORKSPACE, 
> newIndexName=WORKSPACE_ID_ACCOUNT_ID_IDX, existingIndexName=_key_PK, 
> existingIndexColumns=[ID, ACCOUNTID]]
> {noformat}
> But PK and index have different order!



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

[jira] [Commented] (IGNITE-13376) Primary index can be created with fields sequence differ from declared.

2020-08-21 Thread Ignite TC Bot (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181815#comment-17181815
 ] 

Ignite TC Bot commented on IGNITE-13376:


{panel:title=Branch: [pull/8172/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8172/head] Base: [master] : New Tests 
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5556518]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite: 
BasicIndexMultinodeTest.testCorrectPkFldsSequence - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite: 
BasicIndexTest.testCorrectPkFldsSequence - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite: 
BasicIndexMultinodeTest.testCorrectFieldsSequenceInPk - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite: 
BasicIndexTest.testCorrectFieldsSequenceInPk - PASSED{color}

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5556547buildTypeId=IgniteTests24Java8_RunAll]

> Primary index can be created with fields sequence differ from declared.
> ---
>
> Key: IGNITE-13376
> URL: https://issues.apache.org/jira/browse/IGNITE-13376
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7.6, 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce: 
> Execute the following DDL (create table + create index):
> {noformat}
> CREATE TABLE IF NOT EXISTS Workspace (
> id UUID NOT NULL,
> accountId UUID NOT NULL,
> jsonModel VARCHAR,
> PRIMARY KEY (accountId, id)
>   ) WITH 
> "template=partitioned,atomicity=transactional,key_type=org.gridgain.gmc.dto.workspace.WorkspaceKey,value_type=workspace.Workspace,cache_name=WorkspaceCache";
> CREATE INDEX IF NOT EXISTS workspace_id_account_id_idx ON Workspace (id, 
> accountId);
> {noformat}
> On node start got the following warning:
> {noformat}
> Index with the given set or subset of columns already exists (consider 
> dropping either new or existing index) [cacheName=WorkspaceCache, 
> schemaName=PUBLIC, tableName=WORKSPACE, 
> newIndexName=WORKSPACE_ID_ACCOUNT_ID_IDX, existingIndexName=_key_PK, 
> existingIndexColumns=[ID, ACCOUNTID]]
> {noformat}
> But PK and index have different order!



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