trafodion-codereview mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robertamarton <>
Subject [GitHub] incubator-trafodion pull request: Support for features described i...
Date Fri, 04 Sep 2015 17:38:06 GMT
GitHub user robertamarton opened a pull request:

    Support for features described in JIRA TRAFODION-19 && TRAFODION-1483


You can merge this pull request into a Git repository by running:

    $ git pull master

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #74
commit 2e0b1ddf10efbd09fe027ce3af00aef7ba821271
Author: Roberta Marton <>
Date:   2015-09-04T17:09:32Z

    Made the following changes:
    Removed support for locklength from the parser
    Test and fix issues with create table variants
    Made recommended changes as mentioned in the initial delivery
      Rename some of the variable names to make them more informative
      Assume prefix length for HIVE and HBASE tables can be different and verify code works
      Fix commented code to be correct and remove lines no longer needed
      Update error text for messages 1180 to include external table type
    Beefed up the new regression test (hive/TEST009)
    Check column list from hive descriptor with external table description and return an error
if there is a mismatch
    Add an error if the user specifies a different target schema name than the source
    Allow someone with privileges to drop HIVE exernal schemas
    Added support for external HBase tables similar to Hive table support

commit 569045b4fb816e598f5ec1e1bed45894aebf199d
Author: Roberta Marton <>
Date:   2015-09-04T17:11:13Z

    Merge branch 'master' of


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message