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 Wed, 24 Aug 2011 19:34:29 GMT

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

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

I'd be willing to take this one. The only thing I wanted to throw out there, is the solution
I was planning on creating would:

1. Create the database if it doesn't exist
2. Then it would import that data directly into the new database.

Alternative approaches that I think would be reasonable would be just to provide some easy
way in HIVE to change the database of a table easily.

Another thing to consider is whether or not we should be creating databases(Step 1). In mysql
land this would be odd, but it seems as though databases in hive are mostly syntactic sugar,
as you can easily select/join between them.

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