You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Stanilovsky Evgeny (Jira)" <ji...@apache.org> on 2020/08/19 14:19:00 UTC

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

Stanilovsky Evgeny created IGNITE-13376:
-------------------------------------------

             Summary: 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.8.1, 2.7.6
            Reporter: Stanilovsky Evgeny
            Assignee: Stanilovsky Evgeny


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)