tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "JaeHwa Jung (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-284) Add table partitioning entry to Catalog
Date Fri, 15 Nov 2013 06:01:22 GMT

    [ https://issues.apache.org/jira/browse/TAJO-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823325#comment-13823325

JaeHwa Jung commented on TAJO-284:

I designed two types of table schema for this issue as follows:

- master table
In this case, master table includes informations for table partition. And expressions for
partition will be saved by json type.
||Column Name||Column Type||Remark||
|TABLE_ID|varchar(255)| |
|PARTITON_ID|int(11)| |
|TYPE|char(1)|0:HASH, 1:RANGE, 2:LIST, 3:COLUMN|
|EXPRESSIONS}|text|written by json type|

- master table and expressions table
master table includes informations except expressions. expressions table includes informations
for partition key expressions.
||Column Name||Column Type||Remark||
|TABLE_ID|varchar(255)| |
|PARTITON_ID|int(11)| |
|TYPE|char(1)|0:HASH, 1:RANGE, 2:LIST, 3:COLUMN|
||Column Name||Column Type||Remark||
|PARTITON_ID|int(11)| |
|EXPRESSION_ID|int(11)| |
|COLUMN_NAME|varchar(255)| |
|OPERAND|char(1)|0:less than, 1:in|
|VALUES|varchar(255)| |

How about above design? You are welcome to another opinion. :)

> Add table partitioning entry to Catalog
> ---------------------------------------
>                 Key: TAJO-284
>                 URL: https://issues.apache.org/jira/browse/TAJO-284
>             Project: Tajo
>          Issue Type: Sub-task
>          Components: catalog
>            Reporter: Hyunsik Choi
>            Assignee: JaeHwa Jung
>             Fix For: 0.8-incubating
> To support table partitioning, Tajo catalog should supports the table partitioning. Each
partition entry should include partition table id, partition key ids, partition types (i.e.,
hash, range, list, and key), partition number, min, max, and hash id.

This message was sent by Atlassian JIRA

View raw message