[
https://issues.apache.org/jira/browse/SQOOP-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222199#comment-14222199
]
Joey Echeverria commented on SQOOP-1779:
----------------------------------------
+1 on the patch. I filed [CDK-785|https://issues.cloudera.org/browse/CDK-785]
to improve the logging on the Kite side. I think it'd still make sense to
improve the logging in Sqoop as setting HIVE_HOME won't work in all uses of
Kite, but will work here.
> Fix Hive Import handling for Parquet data files
> -----------------------------------------------
>
> Key: SQOOP-1779
> URL: https://issues.apache.org/jira/browse/SQOOP-1779
> Project: Sqoop
> Issue Type: Bug
> Components: hive-integration
> Affects Versions: 1.4.5
> Reporter: Josh Wills
> Attachments: SQOOP-parq-hive.patch
>
>
> When importing Parquet-formatted data files into Hive, Sqoop leaves the
> creation of the tables in the metastore to Kite. Unfortunately, the format of
> the Kite dataset URI for Hive doesn't include the value of the
> --hive-database option and it only knows how to set the table name from the
> --hive-table-name option, instead of just using the name of the table being
> imported.
> As an additional note, running the Parquet importer when HIVE_HOME isn't set
> causes the import job to fail in a way that isn't very helpful in diagnosing
> the underlying issue (i.e., that Kite can't find the Hive jars on the
> classpath.) It would be worthwhile to add better logging to that effect,
> although I'm not sure if that should be done in Kite or in Sqoop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
