[ https://issues.apache.org/jira/browse/PHOENIX-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023306#comment-17023306 ]
Hadoop QA commented on PHOENIX-5697: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12991779/PHOENIX-5697.master.000.patch against master branch at commit 8edbe9deeb666c78962eefd3c57f9bdf82dc8a07. ATTACHMENT ID: 12991779 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-PHOENIX-Build/3341//testReport/ Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/3341//console This message is automatically generated. > Avoid resource leakage with try-with-resources > ---------------------------------------------- > > Key: PHOENIX-5697 > URL: https://issues.apache.org/jira/browse/PHOENIX-5697 > Project: Phoenix > Issue Type: Improvement > Affects Versions: 5.1.0, 4.15.1 > Reporter: Viraj Jasani > Assignee: Viraj Jasani > Priority: Major > Labels: phoenix-hardening > Attachments: PHOENIX-5697.master.000.patch > > > There are places where we catch IOException in finally block while closing a > closable resource or have to do redundant null check. If we could use > try-with-resources to deal with closure of resources, that would not let us > worry about catching IOException or NPE while closing the resources and would > be a better replacement. -- This message was sent by Atlassian Jira (v8.3.4#803005)