Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tajo.incubator.apache.org
Date: Fri, 6 Dec 2013 07:06:36 +0000 (UTC)
From: "Hyunsik Choi (JIRA)" <jira@apache.org>
To: dev@tajo.incubator.apache.org
Message-ID: <JIRA.12678937.1384320485689.83570.1386313596544@arcas>
In-Reply-To: <JIRA.12678937.1384320485689@arcas>
References: <JIRA.12678937.1384320485689@arcas>
Subject: [jira] [Updated] (TAJO-304) drop table command should not remove
 data files in default
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hyunsik Choi updated TAJO-304:
------------------------------

    Attachment: TAJO-304.patch

I changed the plan. I modified DDL statement as follows:
{code}
DROP TABLE table_name [PURGE]
{code}

PURGE is given, 'DROP TABLE' deletes the table from catalog and purges all data. Otherwise, 'DROP TABLE' just deletes a table from catalog.

> drop table command should not remove data files in default
> ----------------------------------------------------------
>
>                 Key: TAJO-304
>                 URL: https://issues.apache.org/jira/browse/TAJO-304
>             Project: Tajo
>          Issue Type: Improvement
>          Components: catalog, master
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.8-incubating
>
>         Attachments: TAJO-304.patch
>
>
> h3. Problem
> In the current implementation, Tajo removes a data directory when a user issues 'drop table' command. But, it is very dangerous in many cases. For example, some users may lost large data sets.
> h3. Solution
> In default, Tajo should not remove a data directory, and we need to add a config property 'tajo.command.drop_table.data_removal' for those who want to change the behavior of 'drop table'.


--
This message was sent by Atlassian JIRA
(v6.1#6144)