[jira] [Reopened] (HADOOP-8486) Resource leak - Close the open resource handles (File handles) before throwing the exception from the SequenceFile constructor

["Bikas Saha (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bikas Saha reopened HADOOP-8486:
--------------------------------


This has caused build failure because Path.getUriPath is no longer available.
    [javac] c:\Users\bikas\Code\hdp\src\test\org\apache\hadoop\io\TestSequenceFile.java:59: cannot find symbol
    [javac] symbol  : method getUriPath()
    [javac] location: class org.apache.hadoop.fs.Path
    [javac]     File f = new File(nonSeqFile.getUriPath());
                
> Resource leak - Close the open resource handles (File handles) before throwing the exception from the SequenceFile constructor
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8486
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8486
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs, io
>    Affects Versions: 1.0.2, 1-win
>            Reporter: Kanna Karanam
>            Assignee: Kanna Karanam
>             Fix For: 1-win
>
>         Attachments: HADOOP-8486-branch-1-win-(2).patch, HADOOP-8486-branch-1-win-(3).patch, HADOOP-8486-branch-1-win-(4).patch, HADOOP-8486-branch-1-win.patch
>
>
> I noticed this problem while I am working on porting HIVE to work on windows. Hive is attempting to create this class object to validate the file format and end up with resource leak. Because of this leak, we can’t move, rename or delete the files on windows when there is an open file handle whereas in UNIX we can perform all these operation with no issues even with open file handles.
> Please suggest me if you similar issues in any other places.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira