[
https://issues.apache.org/jira/browse/TAJO-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973728#comment-13973728
]
Hyunsik Choi edited comment on TAJO-744 at 4/18/14 2:50 AM:
------------------------------------------------------------
Currently, Tajo only supports column partition.
You can just use the current partition entry schema. Also, I thought that you
may want some change of partition entry schema. If you do so, it would be
better if you change the partition entry schema to be specified for only column
partition without considering other partition types like range. It's because we
can make range or hash partition schemas as separate ones later. I intended it.
:)
Also, I don't think that you need to design range and hash partition schemas in
this issue.
Best Regards,
Hyunsik
was (Author: hyunsik):
Currently, Tajo only supports column partition.
You can just use the current partition entry schema. Also, I thought that you
may want some change of partition entry schema. If you do so, it would be
better if you change the partition entry schema specified for only column
partition without considering other partition types like range. It's because we
can make range or hash partition schemas as separate ones later. I intended it.
:)
Also, I don't think that you need to design range and hash partition schemas in
this issue.
Best Regards,
Hyunsik
> ALTER TABLE ADD/DROP PARTITION statement
> ----------------------------------------
>
> Key: TAJO-744
> URL: https://issues.apache.org/jira/browse/TAJO-744
> Project: Tajo
> Issue Type: New Feature
> Components: catalog
> Affects Versions: 0.9
> Reporter: Hyunsik Choi
> Assignee: Alvin Henrick
> Fix For: 0.9
>
>
> Currently, Tajo does not manage partitioned directly. In Tajo, each partition
> is just a directory. For each query, a logical planner traverses matched
> directories in HDFS according to partition predicates.
> This approach is not efficient especially in the environment where the number
> of partitions are very large. It also makes partition management hard.
> Tajo should manage partitions directly by using ALTER TABLE ADD/DROP
> PARTITION statements. A number of partition entries should be stored in the
> underlying database that catalog uses.
> {code:title=Synopsis of ALTER TABLE ADD/DROP PARTITION}
> ALTER TABLE table_name [IF NOT EXISTS] ADD COLUMN PARTITION (key1 = 'val2',
> key2 = 'val2', ...) WITH ('prop_key' = 'prop_val', ...) LOCATION '...';
> ALTER TABLE table_name [IF EXISTS] DROP COLUMN PARTITION (key1
> [=|<|<=|>|>=|!=] 'val1');
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
