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

Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2017/08/21 16:06:00 UTC

[jira] [Resolved] (KUDU-2016) Altered column DEFAULTs don't show up in metadata

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

Will Berkeley resolved KUDU-2016.
---------------------------------
    Resolution: Fixed

> Altered column DEFAULTs don't show up in metadata
> -------------------------------------------------
>
>                 Key: KUDU-2016
>                 URL: https://issues.apache.org/jira/browse/KUDU-2016
>             Project: Kudu
>          Issue Type: Bug
>          Components: client
>            Reporter: Thomas Tauber-Marshall
>            Assignee: Will Berkeley
>            Priority: Critical
>              Labels: impala
>             Fix For: 1.4.0
>
>         Attachments: KuduTest.java
>
>
> A recent change (KUDU-861) added the ability to alter column defaults. However, after altering a default, accessing the table's metadata does not reflect the new default in the ColumnSchema.
> The new default is applied correctly to newly inserted rows, and other attributes that can be altered from that patch, ENCODING, COMPRESSION, and BLOCK_SIZE, show up in the metadata correctly.
> A small repro is attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)