[
https://issues.apache.org/jira/browse/TAJO-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825041#comment-13825041
]
Hyunsik Choi commented on TAJO-284:
-----------------------------------
Here are comments for both design:
* The name PARTITIONS would be better than PARTITION.
* TID is a primary key of TABLES. So, TID would be better than TABLE_ID.
* partition name is missing. Each hash and range partition can have its
partition name.
I prefer the first design because it looks more scalable. As you know, we need
to consider more than 10 million partitions. The second design involves join
operation. It may be less scalable than the first one.
Additionally, we need to consider access pattern from a given query. Given a
query with some filter conditions. Catalog will find matched partitions with
filter condition. Especially, EXPRESSIONS field should be efficiently
searchable from some range filter.
> 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)
