hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gelesh (JIRA)" <>
Subject [jira] [Commented] (HIVE-1918) Add export/import facilities to the hive system
Date Thu, 04 Jul 2013 07:36:20 GMT


Gelesh commented on HIVE-1918:

Can We have a option to copy meta information alone,

So that, during DistCp with out copying the Hive files, (with partition folder and clustered
file structure) to a temp location, we can create a _meta file alone.

Then, DistCp the hive files (the partioned and clusteded file structure) as such and load
re create a hive table in the new cluster.
> Add export/import facilities to the hive system
> -----------------------------------------------
>                 Key: HIVE-1918
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore, Query Processor
>            Reporter: Krishna Kumar
>            Assignee: Krishna Kumar
>             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
> 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
for these details.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message