tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAJO-220) Implement catalog dump feature
Date Fri, 04 Oct 2013 11:10:43 GMT

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

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

    Attachment: TAJO-220_2.patch

Thank you for your comments. I've handled the missing license problem.

> 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_2.patch, 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)

Mime
View raw message