[
https://issues.apache.org/jira/browse/SQOOP-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222243#comment-14222243
]
Hudson commented on SQOOP-1779:
-------------------------------
SUCCESS: Integrated in Sqoop-ant-jdk-1.6-hadoop200 #959 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop200/959/])
SQOOP-1779: Add support for --hive-database when importing Parquet files into
Hive (jarcec:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=52604b1661a8e4e32dec759343f6c72b8546766e)
* src/java/org/apache/sqoop/mapreduce/DataDrivenImportJob.java
> Add support for --hive-database when importing Parquet files into Hive
> ----------------------------------------------------------------------
>
> 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
> Assignee: Josh Wills
> Fix For: 1.4.6
>
> 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)
