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

Roman Puchkovskiy updated IGNITE-20906:
---------------------------------------
    Description: 
CREATE TABLE t (id INT PRIMARY KEY, val INT NOT NULL);

ALTER TABLE t ALTER COLUMN val SET DATA TYPE BIGINT;

Second query fails with the following message 'Changing the precision for 
column of type 'INT32' is not allowed', alghough precision is not mentioned in 
any of the queries.

Same thing happens when trying to change SMALLINT -> INT.

IEP: 
[https://cwiki.apache.org/confluence/display/IGNITE/IEP-108+Change+column+type#IEP108Changecolumntype-Datavalidation.]

  was:
CREATE TABLE t (id INT PRIMARY KEY, val INT NOT NULL);

ALTER TABLE t ALTER COLUMN val SET DATA TYPE BIGINT;

Second query fails with the following message 'Changing the precision for 
column of type 'INT32' is not allowed', alghough precision is not mentioned in 
any of the queries.

Same thing happens when trying to change SMALLINT -> INT.


> Attempt to change column type from INT to BIGINT fails
> ------------------------------------------------------
>
>                 Key: IGNITE-20906
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20906
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Roman Puchkovskiy
>            Assignee: Evgeny Stanilovsky
>            Priority: Major
>              Labels: ignite-3
>
> CREATE TABLE t (id INT PRIMARY KEY, val INT NOT NULL);
> ALTER TABLE t ALTER COLUMN val SET DATA TYPE BIGINT;
> Second query fails with the following message 'Changing the precision for 
> column of type 'INT32' is not allowed', alghough precision is not mentioned 
> in any of the queries.
> Same thing happens when trying to change SMALLINT -> INT.
> IEP: 
> [https://cwiki.apache.org/confluence/display/IGNITE/IEP-108+Change+column+type#IEP108Changecolumntype-Datavalidation.]



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

Reply via email to