[
https://issues.apache.org/jira/browse/TAJO-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973665#comment-13973665
]
Hyunsik Choi commented on TAJO-744:
-----------------------------------
Hi Alvin,
It would be a key feature for Tajo.
I'd like to hear what you think about the current Derby/MySQL schema for
partition entries. You can use the current schema or you can improve it. As you
know, we have a plan to add range and hash partition in the near future. The
current schema is designed to deal with all kinds of partition types. I'd like
to propose to separate the consolidated schema into multiple schemas designed
for their specified usage patterns. If so, we would make good use of indexing
techniques according to the index characteristics.
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)
