Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 23 Dec 2013 23:14:52 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12684372.1386890016530.6310.1387840492314@arcas>
In-Reply-To: <JIRA.12684372.1386890016530@arcas>
References: <JIRA.12684372.1386890016530@arcas>
Subject: [jira] [Commented] (ACCUMULO-2010) Remove resource leak warnings
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Tubbs commented on ACCUMULO-2010:
---------------------------------------------

Adding the following comment for completeness, not to start an additional thread about this (since we already have one on the mailing list).

The visibility of the warnings may be IDE-specific. It just so happened that this issue was represented as warnings in my IDE... but the impact on the API by having Closeable declared, but not actually used by our own code, or having clear semantics is a problem independent of how they manifest (or not) in an IDE.

> Remove resource leak warnings
> -----------------------------
>
>                 Key: ACCUMULO-2010
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2010
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.4.5, 1.5.1, 1.6.0
>
>
> ACCUMULO-1984 introduced a lot of resource leak warnings, because it made Instance implement Closeable. If we really want this instance to be Closeable, then we need to close it when we're done with it, to set a good example for using the API, at the very least.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)