Return-Path: X-Original-To: apmail-tajo-dev-archive@minotaur.apache.org Delivered-To: apmail-tajo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 86AE510DE6 for ; Mon, 18 Nov 2013 02:41:46 +0000 (UTC) Received: (qmail 60839 invoked by uid 500); 18 Nov 2013 02:41:45 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 60810 invoked by uid 500); 18 Nov 2013 02:41:45 -0000 Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.incubator.apache.org Delivered-To: mailing list dev@tajo.incubator.apache.org Received: (qmail 60801 invoked by uid 99); 18 Nov 2013 02:41:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Nov 2013 02:41:45 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 18 Nov 2013 02:41:43 +0000 Received: (qmail 60766 invoked by uid 99); 18 Nov 2013 02:41:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Nov 2013 02:41:22 +0000 Date: Mon, 18 Nov 2013 02:41:22 +0000 (UTC) From: "JaeHwa Jung (JIRA)" To: dev@tajo.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (TAJO-284) Add table partitioning entry to Catalog MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/TAJO-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825046#comment-13825046 ] JaeHwa Jung commented on TAJO-284: ---------------------------------- Thanks Hyunsik. I agree with your opinion. I think that a given query will be more useful better than structured columns. So, I modified the design as follows: h5. PARTITION ||Column Name||Column Type||Remark|| |PARTITION_ID|int(11)| | |PARTITION_NAME|varchar(255)| | |TID|int(11)| | |TYPE|char(1)|0:HASH, 1:RANGE, 2:LIST, 3:COLUMN, and so on| |EXPRESSIONS|text|a partition definition phase at a given query| \\ A range partition sample is as follows: h5. Given query {code:xml} CREATE TABLE sales ( col1 int, col2 int) PARTITION BY RANGE (col1) ( PARTITION col1 VALUES LESS THAN (2), PARTITION col1 VALUES LESS THAN (5), PARTITION col1 VALUES LESS THAN (MAXVALUE) ); {code} h5. PARTITION ||Column Name||Value|| |PARTITION_ID|10| |PARTITION_NAME|RANGE_PARTITION| |TID|1| |TYPE|1| |EXPRESSIONS|PARTITION BY RANGE (col1) ( PARTITION col1 VALUES LESS THAN (2), PARTITION col1 VALUES LESS THAN (5), PARTITION col1 VALUES LESS THAN (MAXVALUE) );| > 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)