[
https://issues.apache.org/jira/browse/PHOENIX-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032678#comment-17032678
]
Hudson commented on PHOENIX-5697:
---------------------------------
SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-1.4 #389 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.4/389/])
PHOENIX-5697 : Use try-with-resources to avoid leakage (chinmayskulkarni: rev
8ccd57b27acf80357e8ccf71a18f8d89110e7e35)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/write/TrackingParallelWriterIndexCommitter.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/MetaDataUtil.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/write/AbstractParallelWriterIndexCommitter.java
> 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
> Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0
>
> Attachments: PHOENIX-5697.4.x-HBase-1.5.000.patch,
> PHOENIX-5697.master.000.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
