[
https://issues.apache.org/jira/browse/SQOOP-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560292#comment-13560292
]
Hudson commented on SQOOP-813:
------------------------------
Integrated in Sqoop2-hadoop200 #138 (See
[https://builds.apache.org/job/Sqoop2-hadoop200/138/])
SQOOP-813: LoaderExecutor might get into deadlock when exception is raised
outside Loader itself (Revision 5be8eb680867d26c5ec23a4501eca3d8bb031e54)
Result = SUCCESS
cheolsoo :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=5be8eb680867d26c5ec23a4501eca3d8bb031e54
Files :
*
execution/mapreduce/src/main/java/org/apache/sqoop/job/mr/SqoopOutputFormatLoadExecutor.java
> Sqoop2: LoaderExecutor might get into deadlock when exception is raised
> outside Loader itself
> ---------------------------------------------------------------------------------------------
>
> Key: SQOOP-813
> URL: https://issues.apache.org/jira/browse/SQOOP-813
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.1
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.2
>
> Attachments: SQOOP-813.patch
>
>
> We have loader execution in LoaderExecutor protected by try-catch block,
> however additional computation performed by Sqoop framework are not protected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
