hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1444) Sqoop ConnManager instances can leak Statement objects
Date Thu, 18 Feb 2010 16:25:28 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835273#action_12835273
] 

Hudson commented on MAPREDUCE-1444:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #239 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/239/])
    

> Sqoop ConnManager instances can leak Statement objects
> ------------------------------------------------------
>
>                 Key: MAPREDUCE-1444
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1444
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/sqoop
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>             Fix For: 0.22.0
>
>         Attachments: MAPREDUCE-1444.patch
>
>
> The ConnManager API returns ResultSets to users but does not provide a mechanism to clean
up the underlying Statement that generated the ResultSet. Problematically, closing the Statement
will invalidate the ResultSet, so these must be cleaned up in LIFO order, putting the onus
on the receiver of the ResultSet.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message