[
https://issues.apache.org/jira/browse/HCATALOG-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510433#comment-13510433
]
Mithun Radhakrishnan commented on HCATALOG-560:
-----------------------------------------------
There was one suggestion that we provide a more general API, as follows:
{{public void updateTableSchema(String db, String table, List<HCatFieldSchema>
newSchema) throws HCatException;}}
This will be more general than {"ALTER TABLE ... ADD COLUMN"}}, allowing a
glorious future where columns may be removed, redefined or replaced. At the
same time, we don't go so far as to offer the full functionality of
{{HSMC::alter_table()}} (that could well change even the partitioning-schema of
the table.)
> HCatClient should support addition of new columns to a Table.
> -------------------------------------------------------------
>
> Key: HCATALOG-560
> URL: https://issues.apache.org/jira/browse/HCATALOG-560
> Project: HCatalog
> Issue Type: Improvement
> Components: client
> Affects Versions: 0.4.1
> Reporter: Mithun Radhakrishnan
> Assignee: Mithun Radhakrishnan
> Fix For: 0.5, 0.4.1
>
>
> HCatClient currently doesn't support the modification of a Table schema to
> support new columns. (The equivalent of "ALTER TABLE ... ADD COLUMN(...)".)
> This is required by systems that need to support evolving data-schemas. If
> one considers the simplified case of only appending columns to the end of a
> table's schema-definition, it should be easy to provide and implement the
> following API in terms of HMSClient::alter_table():
> {{public void appendColumnsToTable(String db, String table,
> List<HCatFieldSchema> newColumns) throws HCatException;}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
