[
https://issues.apache.org/jira/browse/SQOOP-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139292#comment-14139292
]
Pratik Khadloya commented on SQOOP-1520:
----------------------------------------
For Hive 0.13
I tested it again with this patch from trunk. It got further now, but still
fails with "Hive table lookup exception". It is able to create the hive table
in the right hive metastore (shared mysql) as i can see it in hue, but not sure
why it boots up a local metastore in the logs.
I suspect it is creating in the right metastore, but looking up in the wrong
one.
Logs: https://gist.github.com/tispratik/e9ee14b072bf36d7ea0d
Can you please take a look?
> The table is null when using import into hive as parquet file and query option
> ------------------------------------------------------------------------------
>
> Key: SQOOP-1520
> URL: https://issues.apache.org/jira/browse/SQOOP-1520
> Project: Sqoop
> Issue Type: Bug
> Components: hive-integration
> Affects Versions: 1.4.5
> Reporter: Richard
> Assignee: Richard
> Fix For: 1.4.6
>
> Attachments: diff.patch
>
>
> {code}
> sh sqoop import --connect jdbc:mysql://server-391/test --username admin
> --password admin --target-dir /user/pkhadloya/sqoop/extusersegments
> --hive-import --hive-table extusersegments --create-hive-table
> --as-parquetfile --query "select * from test where \$CONDITIONS" --split-by id
> {code}
> {code:title=hive}
> 0: jdbc:hive2://server-393:10000/default> show tables;
> +-----------+--+
> | tab_name |
> +-----------+--+
> | null |
> +-----------+--+
> 1 row selected (0.041 seconds)
> 0: jdbc:hive2://server-393:10000/default> select * from null;
> +----------+------------+--+
> | null.id | null.name |
> +----------+------------+--+
> | 1 | richard |
> +----------+------------+--+
> 1 row selected (2.062 seconds)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
