Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 347B1200D2D for ; Fri, 27 Oct 2017 17:45:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3309E1609E9; Fri, 27 Oct 2017 15:45:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 79443160BDC for ; Fri, 27 Oct 2017 17:45:04 +0200 (CEST) Received: (qmail 70476 invoked by uid 500); 27 Oct 2017 15:45:03 -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 70465 invoked by uid 99); 27 Oct 2017 15:45:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Oct 2017 15:45:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id BF8EDC7B31 for ; Fri, 27 Oct 2017 15:45:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id xWR5R_ZkZBkz for ; Fri, 27 Oct 2017 15:45:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 7D7C65FB2D for ; Fri, 27 Oct 2017 15:45:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id BCA0CE0A3A for ; Fri, 27 Oct 2017 15:45:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 7CE31212F9 for ; Fri, 27 Oct 2017 15:45:00 +0000 (UTC) Date: Fri, 27 Oct 2017 15:45:00 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-4729) MiniAccumuloCluster should have a Singleton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 27 Oct 2017 15:45:05 -0000 [ https://issues.apache.org/jira/browse/ACCUMULO-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222579#comment-16222579 ] Christopher Tubbs commented on ACCUMULO-4729: --------------------------------------------- There are two ways I've seen MiniAccumuloCluster shared with multiple tests: 1. A JUnit test having a {{@BeforeClass}} section to start the cluster, and an {{@AfterClass}} section to stop it, with multiple {{@Test}} methods to each run a test. 2. Using {{accumulo-maven-plugin}} to launch (Mini)Accumulo at the {{pre-integration-test}} phase of the Maven build lifecycle, and run many tests during the {{integration-test}} phase, with the {{maven-failsafe-plugin}}, and then shut down at {{post-integration-test}} just before integration tests are validated in the {{verify}} phase. If MiniAccumuloCluster were made to have a singleton, I'm not sure it would be clear who would be responsible for managing its lifecycle (shutting it down, starting it, etc.). And, this would be especially weird if we still allowed {{new MiniAccumuloCluster}}s to be launched separately from this singleton. That could be confusing. For your use case, is it possible for you to simple assign {{new MiniAccumuloCluster}} to a variable, which you share with all your tests? That seems like the best solution to me. > MiniAccumuloCluster should have a Singleton > ------------------------------------------- > > Key: ACCUMULO-4729 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4729 > Project: Accumulo > Issue Type: Bug > Components: mini > Affects Versions: 1.8.1 > Reporter: Jorge Machado > Priority: Minor > > As developer I would like to have something like MiniAccumuloCluster.getInstance() > That I can share with multiple tests -- This message was sent by Atlassian JIRA (v6.4.14#64029)