You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Andrew Chalfant (JIRA)" <ji...@apache.org> on 2012/08/05 04:40:04 UTC

[jira] [Commented] (HIVE-3068) Add ability to export table metadata as JSON on table drop

    [ https://issues.apache.org/jira/browse/HIVE-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428776#comment-13428776 ] 

Andrew Chalfant commented on HIVE-3068:
---------------------------------------

Okay, I have updated the diff to take parameterized locations and whether or not the file is deleted, so that we can test the existence of the subfolder int he export location with dfs -rmr (which throws and error if the path doesn't exist). This should resolve the issues you brought up last time. 
                
> Add ability to export table metadata as JSON on table drop
> ----------------------------------------------------------
>
>                 Key: HIVE-3068
>                 URL: https://issues.apache.org/jira/browse/HIVE-3068
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore, Serializers/Deserializers
>            Reporter: Andrew Chalfant
>            Assignee: Andrew Chalfant
>            Priority: Minor
>              Labels: features, newbie
>         Attachments: HIVE-3068.2.patch.txt
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When a table is dropped, the contents go to the users trash but the metadata is lost. It would be super neat to be able to save the metadata as well so that tables could be trivially re-instantiated via thrift.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira