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

Posted to issues@kudu.apache.org by "Dimitris Tsirogiannis (JIRA)" <ji...@apache.org> on 2016/11/15 06:52:59 UTC

[jira] [Created] (KUDU-1747) AlterTableOptions.addColumns() API has wrong semantics wrt nullability and default values

Dimitris Tsirogiannis created KUDU-1747:
-------------------------------------------

             Summary: 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


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)