[
https://issues.apache.org/jira/browse/KUDU-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15674753#comment-15674753
]
Will Berkeley commented on KUDU-1747:
-------------------------------------
Review at http://gerrit.cloudera.org:8080/5132
> AlterTableOptions.addColumns() API has wrong semantics wrt nullability and
> default values
> -----------------------------------------------------------------------------------------
>
> Key: KUDU-1747
> URL: https://issues.apache.org/jira/browse/KUDU-1747
> Project: Kudu
> Issue Type: Bug
> Reporter: Dimitris Tsirogiannis
> Assignee: Will Berkeley
>
> The AlterTableOptions class specifies two addColumn() calls in the Java
> client API. The first assumes the added column is non-nullable and hence
> requires a default value. The second assumes that a nullable column should
> not have a default value. However, the semantics of the second addColumn()
> call are not correct as nullability shouldn't preclude the use of a default
> value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
