Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Message-ID: <17259361.116341295646105534.JavaMail.jira@thor>
Date: Fri, 21 Jan 2011 16:41:45 -0500 (EST)
From: "Edward Capriolo (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Commented: (HIVE-1918) Add export/import facilities to the
 hive system
In-Reply-To: <1634891.15891295279392962.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

If partition currently only has one constructor I do not think we add a second constructor, just change it and break the old compatibility. If we do add partParams we should have DDL statements to view and modify these. For a long time there were many things that were added in the create table such as InputFormat or OutputFormat and we had no way to view or modify these besides going directly to the JDBC and changing them. I am not sure if this is the case here, but I do not think we should be adding fields that are not completely manageable. 

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