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

Alvin Henrick commented on TAJO-744:
------------------------------------

Hi Hyunsik, I agree with you let's make a table for each partition type like 
hash_partition and range_partition. I can design the new schema but I think it 
would be better if you guys can provide the new one and I will make the changes 
to the code accordingly.

I am saying this because you guys have been involved from beginning and you 
guys see the bigger picture.Let me know if this is a good thought otherwise I 
will design the schema and send it to you guys for review and then start coding.

What are the existing partition types we support today ?

Thanks!
Warm Regards,
Alvin.

> 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)

Reply via email to