[
https://issues.apache.org/jira/browse/KUDU-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-1522:
------------------------------
Labels: newbie (was: )
> AlterTable Request Fails when adding TIMESTAMP Column with Default Value
> ------------------------------------------------------------------------
>
> Key: KUDU-1522
> URL: https://issues.apache.org/jira/browse/KUDU-1522
> Project: Kudu
> Issue Type: Bug
> Affects Versions: 0.9.0
> Environment: See description - easily reproducible with a simple
> change to test scripts
> Reporter: Ram Mettu
> Priority: Critical
> Labels: newbie
>
> AlterTable Request Fails when adding TIMESTAMP Column with Default Value. It
> crashes Kudu server requiring a restart.
> Adding a Nullable Timestamp column (without a default value) works fine.
> Quick way to reproduce -
> In kudu/java/kudu-client/src/test/java/org/kududb/client/TestKuduTable.java
> testAlterTable() lines ~76 - 80
> Add a col with Timestamp and default value
> ato = new AlterTableOptions()
> .addColumn("testaddmulticolnotnull", Type.INT32, 4)
> .addNullableColumn("testaddmulticolnull", Type.STRING)
> //.addNullableColumn("testaddmulticolTimestampcol", Type.TIMESTAMP);
> .addColumn("testaddmulticolTimestampcol", Type.TIMESTAMP,
> (System.currentTimeMillis() * 1000));
> submitAlterAndCheck(ato, tableName);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
