sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Dmitriev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-934) JDBC Connection can timeout after import but before hive import
Date Thu, 29 May 2014 09:54:02 GMT

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

Andrey Dmitriev commented on SQOOP-934:

Thank you Gwen for clarification. I opened new JIRA for the Oracle case [SQOOP-1329|https://issues.apache.org/jira/browse/SQOOP-1329]

> JDBC Connection can timeout after import but before hive import
> ---------------------------------------------------------------
>                 Key: SQOOP-934
>                 URL: https://issues.apache.org/jira/browse/SQOOP-934
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.4.2
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Raghav Kumar Gautam
>             Fix For: 1.4.4
>         Attachments: SQOOP-934-2.patch, SQOOP-934.patch
> Our current [import rutine|https://github.com/apache/sqoop/blob/trunk/src/java/org/apache/sqoop/tool/ImportTool.java#L385]
imports data into HDFS and then tries to do Hive import. As the connection to the remote server
is opened only once at the begging it might timeout during very long mapreduce job. I believe
that we should ensure that the connection is still valid before performing the hive import.

This message was sent by Atlassian JIRA

View raw message