[
https://issues.apache.org/jira/browse/SQOOP-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283156#comment-13283156
]
Cheolsoo Park commented on SQOOP-489:
-------------------------------------
Hello Jarcec,
Thank you for your comment. I am sorry, but I seems a bit confused about your
concern. Even excluding the partition key from the create table statement, hive
table will still have that column, doesn't it? So this change only applies to
the statement but not applied to the table itself.
Also, unless getColumnNames() is modified, it shouldn't effect the number of
columns in import job. Am I missing something here? Please correct me if I am
wrong.
> 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
>
> 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
