sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cheolsoo Park (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-489) Cannot define partition keys for Hive tables created through Sqoop
Date Tue, 29 May 2012 12:57:23 GMT

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

Cheolsoo Park commented on SQOOP-489:
-------------------------------------

Hi Jarcec, thank you for your kind explanation. Examples always help. :-)

{quote}
I'm concerned that we silently ignored one column in the table and replaced it with constant
value from command line – both values "1" and "4" from original table were lost.
{quote}

I have a quick question. The case that you're describing can be reproduced even now with '--columns
B,C --hive-partition A --hive-partition-value 666', right? In this case, we're also replacing
the column A with a constant value. Are you assuming that this is OK because the user _explicitly_
specified what he/she is doing?

After all, what I am debating is whether or not the Hive table always has to mirror the source
table that it is importing from.
                
> Cannot define partition keys for Hive tables created through Sqoop
> ------------------------------------------------------------------
>
>                 Key: SQOOP-489
>                 URL: https://issues.apache.org/jira/browse/SQOOP-489
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.1-incubating
>            Reporter: Kathleen Ting
>            Assignee: Cheolsoo Park
>         Attachments: SQOOP-489.patch
>
>
> By enabling the table option, Sqoop includes every column in the table in the create
table query, and by enabling the hive-partition-key option, Sqoop blindly appends the "partitioned
by" clause. Now if you specify one of columns in the table in the hive-partition-key, this
will cause a syntax error in Hive.
> For example, if we have a table 'FOO' that has columns 'I' and 'J':
> sqoop create-hive-table --table FOO ...
> will generate the following Hive query:
> CREATE TABLE IF NOT EXISTS `FOO` ( `I` STRING, `J` STRING)
> Now if we add "--hive-partition-key I" to the command, Sqoop generates the following
query:
> CREATE TABLE IF NOT EXISTS `FOO` ( `I` STRING, `J` STRING) PARTITIONED BY (I STRING)
> The problem is that since 'I' is defined twice (once in CRATE TABLE and once in PARTITIONED
BY), this is a syntax error in Hive.
> This correct query would be something like:
> CREATE TABLE IF NOT EXISTS `FOO` (`J` STRING) PARTITIONED BY (I STRING)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message