[
https://issues.apache.org/jira/browse/KUDU-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306992#comment-15306992
]
Will Berkeley commented on KUDU-982:
------------------------------------
No, Kudu does not make that distinction. A nullable column with no default set
has null as the default value. A partial row with no value set for nullable
column X and no default set for column X but that is otherwise valid will be
inserted with value null for column X. Maybe this is unintentional since the
documentation for KuduColumnSpec::RemoveDefault says that, without a default, a
row must always have a value specified for a column at insertion time.
> 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)
