Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CBEA71088B for ; Fri, 13 Dec 2013 22:58:07 +0000 (UTC) Received: (qmail 3312 invoked by uid 500); 13 Dec 2013 22:58:07 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 3290 invoked by uid 500); 13 Dec 2013 22:58:07 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 3281 invoked by uid 99); 13 Dec 2013 22:58:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Dec 2013 22:58:07 +0000 Date: Fri, 13 Dec 2013 22:58:07 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-2010) Remove resource leak warnings MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848028#comment-13848028 ] ASF subversion and git services commented on ACCUMULO-2010: ----------------------------------------------------------- Commit 335f693a4045d2c2501e2ed6ece0493734093143 in branch refs/heads/1.5.1-SNAPSHOT from [~ctubbsii] [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=335f693 ] ACCUMULO-2010 Remove Closeable from interfaces This gets around compiler warnings about resource leaks. This reverts back to the old API semantics, where we are not advising that clients close Instance objects. If it is determined in the future that we should be advising clients to do this, and therefore want to re-introduce the Closeable interface to Instance and the ZooKeeper objects, it should be accompanied by changes that actually close these resources in our own code. We should not be recommending this without following our own recommendation, and adding Closeable to the interface is a recommendation to call the close method. Also clean up additional resource warnings. > Remove resource leak warnings > ----------------------------- > > Key: ACCUMULO-2010 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2010 > Project: Accumulo > Issue Type: Task > Reporter: 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.4#6159)