You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2019/04/26 14:07:00 UTC

[jira] [Commented] (KUDU-2803) support non-primary key type alteration

    [ https://issues.apache.org/jira/browse/KUDU-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826986#comment-16826986 ] 

Grant Henke commented on KUDU-2803:
-----------------------------------

Do you envision only supporting widening types? Is there another database that you think supports type alteration well to use as reference?

> support non-primary key type alteration
> ---------------------------------------
>
>                 Key: KUDU-2803
>                 URL: https://issues.apache.org/jira/browse/KUDU-2803
>             Project: Kudu
>          Issue Type: Improvement
>            Reporter: HeLifu
>            Priority: Major
>
> We know that kudu does not allow the type of a column to be altered right now. But indeed, a very common case is RDMS -> kudu, and there will be type alterations inevitably, especially for small to large types.
> Currently, here are two ways to get rid of this problem:
>  # for the new tables: predefine a large type for every column;
>  # for the existing tables: stop app(write) > add a new column with large type > copy data -> drop old column -> rename new column to old column -> start app;
> However, neither of them is elegant. So, i think it is necessary to support non-primary key type alteration.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)