Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tajo.incubator.apache.org
Date: Tue, 3 Sep 2013 12:30:51 +0000 (UTC)
From: "Hyunsik Choi (JIRA)" <jira@apache.org>
To: dev@tajo.incubator.apache.org
Message-ID: <JIRA.12666463.1377961250254.70790.1378211451681@arcas>
In-Reply-To: <JIRA.12666463.1377961250254@arcas>
References: <JIRA.12666463.1377961250254@arcas>
Subject: [jira] [Updated] (TAJO-144) Implement INSERT OVERWRITE clause
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/TAJO-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi updated TAJO-144:
------------------------------

    Attachment: TAJO-144.patch

I've attached the patch. This patch provides 'INSERT OVERWRITE INTO' statement. This work follows the 'INSERT INTO' semantic of SQL standard.

The semantics are as follows:

{code}
create table t1 (col1 int8, col2 int4, col3 float4);

-- when a target table schema and output schema are equivalent to each other
insert overwrite into t1 select l_orderkey, l_partkey, l_quantity from lineitem;

-- when the output schema are smaller than the target table schema
insert overwrite into t1 select l_orderkey from lineitem;

-- when you want to specify certain target columns
insert overwrite into t1 (col1, col3) select l_orderkey, l_quantity from lineitem;
{code}
                
> Implement INSERT OVERWRITE clause
> ---------------------------------
>
>                 Key: TAJO-144
>                 URL: https://issues.apache.org/jira/browse/TAJO-144
>             Project: Tajo
>          Issue Type: New Feature
>          Components: planner/optimizer
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.2-incubating
>
>         Attachments: TAJO-144.patch
>
>
> 'INSERT INTO' appends data into existing table. In contrast, 'INSERT OVERWRITE' will overwrite existing table data. It is used as an idiom in analytical fields based HDFS. We need it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira