[
https://issues.apache.org/jira/browse/KUDU-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306180#comment-15306180
]
Will Berkeley commented on KUDU-982:
------------------------------------
[~tlipcon]: Took a look at this one because it seemed like fruit hanging low
enough for me to reach. This functionality already exists, because creating a
nullable column means that the column does not have to be specified in an
insert as it will auto-null. Clearing the default on a nullable column will
restore this behavior.
A column can't be made nullable after table creation, so a column can't be made
default null if it was created as non-nullable. That seems ok, especially
because it's a bigger task to allow a non-nullable column to become nullable.
So maybe this can just be resolved? I think the current behavior is what most
users would expect.
> nullable columns should support DEFAULT NULL
> --------------------------------------------
>
> Key: KUDU-982
> URL: https://issues.apache.org/jira/browse/KUDU-982
> Project: Kudu
> Issue Type: Improvement
> Components: api, client, master
> Affects Versions: Private Beta
> Reporter: Todd Lipcon
>
> I don't think we have APIs which work for setting the default to NULL in
> Alter/Create.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
