sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Newman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-322) Allow specification of Hive Database name when operating on Hive table
Date Fri, 09 Sep 2011 01:06:09 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100837#comment-13100837
] 

Alex Newman commented on SQOOP-322:
-----------------------------------

So I played around with this, and I have a patch which works. The user specifies a --hive-db=<db>
and the HiveQL parts are modified appropriately. However, in the process of writing the patch,
I realized that you can do this with the current code base.

sqoop import --connect jdbc:mysql://localhost/foo --table baz --hive-table=foo.baz --hive-import
--create-hive-table

Does exactly what you hope it would do.

> Allow specification of Hive Database name when operating on Hive table 
> -----------------------------------------------------------------------
>
>                 Key: SQOOP-322
>                 URL: https://issues.apache.org/jira/browse/SQOOP-322
>             Project: Sqoop
>          Issue Type: New Feature
>            Reporter: Alex Newman
>            Assignee: Alex Newman
>
> Sqoop Hive-import does not allow the specification of the database within Hive in which
the table is to be created or populated.
> Relevant issue: HIVE-2172

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message