sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arvind Prabhakar (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:38:31 GMT

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

Arvind Prabhakar commented on SQOOP-322:
----------------------------------------

Thanks Alex for taking this up.

I don't think we should be creating a database if it does not exist, which should be an error
condition. The reason being that while in its current state the Hive databases are just a
layer of namespace abstraction, going forward they are likely to evolve towards different
administrative boundaries. 

> 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