You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2024/03/16 07:52:00 UTC

[jira] [Updated] (IGNITE-21353) Sql. Support for choosing the primary key index type.

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

Pavel Pereslegin updated IGNITE-21353:
--------------------------------------
    Fix Version/s: 3.0.0-beta2

> Sql. Support for choosing the primary key index type.
> -----------------------------------------------------
>
>                 Key: IGNITE-21353
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21353
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Iurii Gerzhedovich
>            Assignee: Maksim Zhuravkov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> As of now we support choosing type just for secondary indexes, like a 
> _CREATE INDEX  idx_name ON table *USING TREE* (column_name)_
> But for PK we always create under the hood HASH index.
> Let's introduce ability to choose type for PK by the analogy with a secondary indexes;
> it should be add an optional parameter *USING type* for PRIMARY KEY definition and add ability set collation for columns including into PK)
> CREATE TABLE ..... (..., PRIMARY KEY *[ USING SORTED | HASH ]* (column1, column2, ... column_n)) ...)
> as example full command: CREATE TABLE my (c1 INT, c2 INT, c3 INT, PRIMARY KEY *USING* {*}SORTED{*}{*}{{*}} (c2 ASC, c1 DESC NULL FIRST))
> Also let's set BTREE as default for PK without set concrete type.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)