[
https://issues.apache.org/jira/browse/KUDU-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665837#comment-15665837
]
Todd Lipcon commented on KUDU-1746:
-----------------------------------
yea, while we're at it, we should make API more builder-like instead of having
a bazillion parameters, eg:
....addColumn("foo").encoding(...).compression(...).desiredBlockSize(...)
Otherwise it will be very difficult to maintain this API over time.
> 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
>
> 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)
