[
https://issues.apache.org/jira/browse/HCATALOG-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mithun Radhakrishnan updated HCATALOG-560:
------------------------------------------
Attachment: HCATALOG-560.trunk.patch
HCATALOG-560.branch4.patch
Here's a patch each for trunk and branch-4, along with appropriate tests.
I've taken the liberty of cleaning up some loose ends in HCatClient and
HCatClientHMSImpl. Specifically,
1. DROP_DB_MODE didn't follow Java naming convention for enums.
2. Modified the exception-declarations and dropped ConnectionFailureException
from the signature (because a more general Exception-type has already been
declared.)
3. Cleaned up miscellaneous boolean-expressions
> 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
>
> Attachments: HCATALOG-560.branch4.patch, HCATALOG-560.trunk.patch
>
>
> 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
