[
https://issues.apache.org/jira/browse/KUDU-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-180:
-----------------------------
Assignee: Todd Lipcon
Target Version/s: M4.5, 1.1.0 (was: M4.5)
Priority: Blocker (was: Major)
This is also affecting CreateTable, and is majorly wrong semantics. Changing to
blocker for 1.1.
> Java alter table adds new column with only read-default set
> -----------------------------------------------------------
>
> Key: KUDU-180
> URL: https://issues.apache.org/jira/browse/KUDU-180
> Project: Kudu
> Issue Type: Bug
> Components: client
> Affects Versions: M4
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
>
> When issuing an alter table to add a column with a default, the java client
> is only specifying that default as the "read default". This is contrary to
> what you get in SQL if you do "ALTER TABLE x ADD COLUMN y int DEFAULT 3" --
> it will also apply to the write default (i.e allow you to insert a new row
> without specifying y).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
