carbondata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lionelcao <>
Subject [GitHub] incubator-carbondata pull request #882: [CARBONDATA-936] Parse partition tab...
Date Thu, 04 May 2017 18:03:05 GMT
GitHub user lionelcao opened a pull request:

    [CARBONDATA-936] Parse partition table ddl

    Parse partition table ddl, get partitionInfo and store in carbon table.
    SUPPORT range, list, hash partition
    SUPPORT basic syntax validate, partition info in table properties validate
    NOT SUPPORT partition value validate for now. Maybe support in the future or just let
user confirm.
    NOT SUPPORT range interval partition for now.
    Partition column must be part of the schema.

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

    $ git pull 12-dev_910_2

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 #882
commit c95b311ca2077ef68d4eceddacac633637a9bc1b
Author: lionelcao <>
Date:   2017-04-25T03:50:10Z

    parser hash partition table

commit 28e7981d3dea7570532d50c614e15fafbf98e650
Author: lionelcao <>
Date:   2017-04-25T09:49:18Z

    add partition validate & example

commit 981a3254014af39cbda62b4e7d88c1bf2c92003f
Author: lionelcao <>
Date:   2017-04-25T10:04:53Z

    fix style error

commit 58883d6c3937dacc7976f972cbbd5351fb910c6e
Author: lionelcao <>
Date:   2017-04-27T03:24:32Z

    fix style error

commit 6677497e7ab9ceffe30e6239f5c7b0162616a317
Author: lionelcao <>
Date:   2017-05-04T14:50:12Z

    add range partition

commit 3e7c23052443ffa01ea6f7877547561ed0d6045e
Author: lionelcao <>
Date:   2017-05-04T17:47:29Z

    add range/list parser


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