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

Edward Capriolo commented on HIVE-1918:
---------------------------------------


{quote}
But I am not adding new aspects to either model, so if indeed we need to 
address current manageability gaps, should they not be addressed via another 
enhancement request, rather than this one, which aims simply to add 
export/import facilities?
{quote}
This depends on the lag time between the feature getting added and the 
enhancement being added. With wishful thinking the two events will be close, 
but history does not always agree. Management becomes more important as 
different people begin using the metastore for different purposes. I believe if 
we add any feature support to manage it completely with DML is mandatory. 
Currently the metastore is changing for security. import-export, and indexes if 
each of these features are only half manageable at time X this will make 
releases awkward and half functional. 

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

Reply via email to