[
https://issues.apache.org/jira/browse/TAJO-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825046#comment-13825046
]
JaeHwa Jung commented on TAJO-284:
----------------------------------
Thanks Hyunsik.
I agree with your opinion. I think that a given query will be more useful
better than structured columns.
So, I modified the design as follows:
h5. PARTITION
||Column Name||Column Type||Remark||
|PARTITION_ID|int(11)| |
|PARTITION_NAME|varchar(255)| |
|TID|int(11)| |
|TYPE|char(1)|0:HASH, 1:RANGE, 2:LIST, 3:COLUMN, and so on|
|EXPRESSIONS|text|a partition definition phase at a given query|
\\
A range partition sample is as follows:
h5. Given query
{code:xml}
CREATE TABLE sales ( col1 int, col2 int)
PARTITION BY RANGE (col1)
(
PARTITION col1 VALUES LESS THAN (2),
PARTITION col1 VALUES LESS THAN (5),
PARTITION col1 VALUES LESS THAN (MAXVALUE)
);
{code}
h5. PARTITION
||Column Name||Value||
|PARTITION_ID|10|
|PARTITION_NAME|RANGE_PARTITION|
|TID|1|
|TYPE|1|
|EXPRESSIONS|PARTITION BY RANGE (col1)
(
PARTITION col1 VALUES LESS THAN (2),
PARTITION col1 VALUES LESS THAN (5),
PARTITION col1 VALUES LESS THAN (MAXVALUE)
);|
> 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
(v6.1#6144)
