[
https://issues.apache.org/jira/browse/TAJO-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855505#comment-13855505
]
Hyunsik Choi commented on TAJO-283:
-----------------------------------
Min,
Thank you for your comment and reminding what Tajo will go. I totally agree
with you, and your suggestion is exactly what we planned. Actually, similar
issues were discussed in TAJO-284. We haven't summarized the detail so far, so
we may need to describe the issue in more detail.
Later, each partition of hash, range, and column partitions will have each row
with indexable and searchable columns in RDBMS for efficient pruning. We should
do that. Currently, Tajo's partition is under heavy development, and we usually
work in a quick-and-dirty manner until release. So, the partition work is under
progress =) In addition, we need 'alter partition' statement and a distributed
plan part in order to complete column-partitioned table support.
I really welcome such suggestions and comments, and please keep going.
Merry Christmas!
> Add Table Partitioning
> ----------------------
>
> Key: TAJO-283
> URL: https://issues.apache.org/jira/browse/TAJO-283
> Project: Tajo
> Issue Type: New Feature
> Components: catalog, physical operator, planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.8-incubating
>
>
> Table partitioning gives many facilities to maintain large tables. First of
> all, it enables the data management system to prune many input data which are
> actually not necessary. In addition, it gives the system more optimization
> opportunities that exploit the physical layouts.
> Basically, Tajo should follow the RDBMS-style partitioning system, including
> range, list, hash, and so on. In order to keep Hive compatibility, we need to
> add Hive partition type that does not exists in existing DBMS systems.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
