Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tajo.incubator.apache.org
Date: Fri, 4 Oct 2013 09:49:42 +0000 (UTC)
From: "Hyunsik Choi (JIRA)" <jira@apache.org>
To: dev@tajo.incubator.apache.org
Message-ID: <JIRA.12671527.1380614247986.12229.1380880182772@arcas>
In-Reply-To: <JIRA.12671527.1380614247986@arcas>
References: <JIRA.12671527.1380614247986@arcas>
Subject: [jira] [Updated] (TAJO-220) Implement catalog dump feature
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hyunsik Choi updated TAJO-220:
------------------------------

    Status: Patch Available  (was: Open)

> Implement catalog dump feature
> ------------------------------
>
>                 Key: TAJO-220
>                 URL: https://issues.apache.org/jira/browse/TAJO-220
>             Project: Tajo
>          Issue Type: New Feature
>          Components: catalog
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>            Priority: Critical
>              Labels: backup, restore
>             Fix For: 0.2-incubating
>
>         Attachments: TAJO-220.patch
>
>
> The current catalog does not support backup and restore feature. Catalog dump feature will print out all tables and others included in catalog as Tajo DDL statements (i.e., SQL) via stdout. It can also be stored as a file via shell redirection.
> Also, we need a script to call catalog dump feature in a convenient way as follows:
> {code}
> $ bin/tajo_dump [table name or db name] > tajo_backup.sql
> {code}


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