[
https://issues.apache.org/jira/browse/HIVE-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985565#action_12985565
]
Krishna Kumar commented on HIVE-1918:
-------------------------------------
@Namit:
1. Do you have any ideas re how we can get an unique, temporary directory name
for use in the test script files? In code of course we can use the
getScratchDir methods, but how to solve this problem in these test scripts?
2. Export/Import, as in the case of Load, operates at file level rather than at
record level. So there are no record-level filters available.
> 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: Query Processor
> Reporter: Krishna Kumar
> Attachments: HIVE-1918.patch.1.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.
-
You can reply to this email to add a comment to the issue online.
