[
https://issues.apache.org/jira/browse/SQOOP-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401822#comment-15401822
]
ASF GitHub Bot commented on SQOOP-2991:
---------------------------------------
GitHub user bonnetb opened a pull request:
https://github.com/apache/sqoop/pull/24
SQOOP-2991 : avoid endless failed Netezza import
see Jira : https://issues.apache.org/jira/browse/SQOOP-2991
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bonnetb/sqoop SQOOP-2991
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sqoop/pull/24.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #24
----
commit 086b3599d1e7e53dd9f3574c0c3b7697dc3c762a
Author: Benjamin BONNET <benjamin.bon...@m4x.org>
Date: 2016-08-01T10:42:16Z
SQOOP-2991 : avoid endless failed Netezza import
----
> Never ending imports from Netezza
> ---------------------------------
>
> Key: SQOOP-2991
> URL: https://issues.apache.org/jira/browse/SQOOP-2991
> Project: Sqoop
> Issue Type: Bug
> Components: connectors
> Affects Versions: 1.4.6
> Reporter: Benjamin BONNET
> Priority: Critical
>
> Hi,
> there are situations where a Netezza import may fail but never end (i.e. the
> map reduce job will run for ever).
> That occurs when Sqoop manages to open a connection to the database and
> executes a query that fails on the Netezza side without writing anything into
> the connection. For instance, that typically occurs for authroization
> problems.
> Then you have to kill the map reuce job by hand if you want to free the
> resource (memory) kept by the MR container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
