You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2016/12/07 16:43:58 UTC
[jira] [Updated] (KUDU-1746) Add support for specifying all
possible column options in AlterTableOptions.addColumn()
[ https://issues.apache.org/jira/browse/KUDU-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Will Berkeley updated KUDU-1746:
--------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
Status: Resolved (was: In Review)
Fixed in 75b1c1578ec6503e02b934a9058f08a1f63e3b4f
> Add support for specifying all possible column options in AlterTableOptions.addColumn()
> ----------------------------------------------------------------------------------------
>
> Key: KUDU-1746
> URL: https://issues.apache.org/jira/browse/KUDU-1746
> Project: Kudu
> Issue Type: Bug
> Reporter: Dimitris Tsirogiannis
> Assignee: Will Berkeley
> Fix For: 1.2.0
>
>
> Currently, AlterTableOptions.addColumn() call allows only name, type and default value to be specified when a new column is added to an existing table. Hence, four API calls are needed in order to fully specify a column that includes column encoding, compression and desired block size. From a usability point of view it would be better if all possible options could be specified using a single call. Impala will make use of a such an API call so that users can specify new columns using a single ALTER TABLE statement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)