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

Hudson commented on SQOOP-2971:
-------------------------------

FAILURE: Integrated in Sqoop-hadoop200 #1058 (See 
[https://builds.apache.org/job/Sqoop-hadoop200/1058/])
SQOOP-2971: OraOop does not close connections properly (Szabolcs Vasas 
(kathleen: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=7808c6bc3e7116534fb2bf83472c8fa8d2d8a0f4])
* src/java/org/apache/sqoop/mapreduce/db/DBInputFormat.java
* src/java/org/apache/sqoop/manager/oracle/OraOopDataDrivenDBInputFormat.java
* 
src/test/org/apache/sqoop/manager/oracle/OraOopDataDrivenDBInputFormatConnectionCloseTest.java
* src/test/com/cloudera/sqoop/ThirdPartyTests.java


> OraOop does not close connections properly
> ------------------------------------------
>
>                 Key: SQOOP-2971
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2971
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Attila Szabo
>            Assignee: Szabolcs Vasas
>             Fix For: 1.4.6, 1.4.7
>
>         Attachments: SQOOP-2971.patch, SQOOP-2971.patch
>
>
> When importing with OraOop for every mapper task two connections are created, 
> and those connections are not closed until the end of the import process, 
> thus Sqoop use twice of the necessary amount, and kinda leaks the expensive 
> resources. This could cause problem when the number of the connections is 
> limited on the DB server side, however the user would like to leverage from 
> having more mappers (e.g. right now with 10 avail connections the user cannot 
> use 10 mappers, but instead only 4).
> Please provide a fix for this issue either by sharing the connection, or 
> closing the connections when they are not needed anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to