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 C2CCA11BB8 for ; Mon, 31 Mar 2014 01:52:19 +0000 (UTC) Received: (qmail 23177 invoked by uid 500); 31 Mar 2014 01:52:17 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 23114 invoked by uid 500); 31 Mar 2014 01:52:15 -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 23087 invoked by uid 99); 31 Mar 2014 01:52:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2014 01:52:15 +0000 Date: Mon, 31 Mar 2014 01:52:15 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-2592) Add new interfaces that better allow extension/implementations of Accumulo clusters 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-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954903#comment-13954903 ] Christopher Tubbs commented on ACCUMULO-2592: --------------------------------------------- That particular experimental annotation was specifically introduced for the configuration. If we need something more broadly than that, I'd prefer we design that in as a public API annotation, not reuse something that was meant for being internal use only. I'd also prefer that we discuss it and explicitly make a decision about how we want to communicate intent to API consumers, so we can document it, rather than simply use something internally and have API consumers make assumptions about what intentions we meant with the use of a particular annotation. > Add new interfaces that better allow extension/implementations of Accumulo clusters > ----------------------------------------------------------------------------------- > > Key: ACCUMULO-2592 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2592 > Project: Accumulo > Issue Type: Improvement > Components: mini > Reporter: Josh Elser > Assignee: Josh Elser > Fix For: 1.6.0 > > Attachments: 0001-ACCUMULO-2592-Create-AccumuloCluster-and-AccumuloCon.patch > > > From the conversation on dev@a.a.o, this is ticket encapsulate additions to the minicluster codebase. These changes decouple the AccumuloMiniCluster implementation from any "programmatically deployed" Accumulo cluster. > It defines an AccumuloConfig and AccumuloCluster, which the existing AccumuloMiniConfig and AccumuloMiniCluster implement with changing the API. These new interfaces and the factory to create implementations of them are marked as experimental and reside in their own package as they are being introduced so late in the 1.6.0 game. > The existing classes which are in the "public api" are not modified -- the only changes made were done internally. The internal MiniAccumuloCluster and MiniAccumuloConfig classes now implement these new interfaces, have appropriate override annotations, and contain a new {{build}} method on the AccumuloConfiguration implementation to simplify the factory. -- This message was sent by Atlassian JIRA (v6.2#6252)