You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Carl Steinbach (Assigned) (JIRA)" <ji...@apache.org> on 2012/02/17 21:48:57 UTC

[jira] [Assigned] (HIVE-1918) Add export/import facilities to the hive system

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

Carl Steinbach reassigned HIVE-1918:
------------------------------------

    Assignee: Carl Steinbach  (was: Krishna Kumar)
    
> Add export/import facilities to the hive system
> -----------------------------------------------
>
>                 Key: HIVE-1918
>                 URL: https://issues.apache.org/jira/browse/HIVE-1918
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore, Query Processor
>            Reporter: Krishna Kumar
>            Assignee: Carl Steinbach
>             Fix For: 0.8.0
>
>         Attachments: HIVE-1918.patch.1.txt, HIVE-1918.patch.2.txt, HIVE-1918.patch.3.txt, HIVE-1918.patch.4.txt, HIVE-1918.patch.5.txt, HIVE-1918.patch.txt, hive-metastore-er.pdf
>
>
> This is an enhancement request to add export/import features to hive.
> With this language extension, the user can export the data of the table - which may be located in different hdfs locations in case of a partitioned table - as well as the metadata of the table into a specified output location. This output location can then be moved over to another different hadoop/hive instance and imported there.  
> This should work independent of the source and target metastore dbms used; for instance, between derby and mysql.
> For partitioned tables, the ability to export/import a subset of the partition must be supported.
> Howl will add more features on top of this: The ability to create/use the exported data even in the absence of hive, using MR or Pig. Please see http://wiki.apache.org/pig/Howl/HowlImportExport for these details.

--
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