[
https://issues.apache.org/jira/browse/KUDU-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Berkeley updated KUDU-1747:
--------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
Status: Resolved (was: In Review)
Fixed in 75b1c1578ec6503e02b934a9058f08a1f63e3b4f
> 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
> Affects Versions: 1.1.0
> Reporter: Dimitris Tsirogiannis
> Assignee: Will Berkeley
> Fix For: 1.2.0
>
>
> 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)
