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 CCDE810568 for ; Tue, 21 Jan 2014 15:34:36 +0000 (UTC) Received: (qmail 55500 invoked by uid 500); 21 Jan 2014 15:34:22 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 55413 invoked by uid 500); 21 Jan 2014 15:34:20 -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 55325 invoked by uid 99); 21 Jan 2014 15:34:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jan 2014 15:34:20 +0000 Date: Tue, 21 Jan 2014 15:34:20 +0000 (UTC) From: "Mike Drob (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-2221) CloudStone Benchmarks should accept ZKs as parameter 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-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated ACCUMULO-2221: -------------------------------- Component/s: docs > CloudStone Benchmarks should accept ZKs as parameter > ---------------------------------------------------- > > Key: ACCUMULO-2221 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2221 > Project: Accumulo > Issue Type: Bug > Components: docs, test > Affects Versions: 1.4.4, 1.5.0 > Reporter: Mike Drob > Assignee: Mike Drob > Labels: newbie > Fix For: 1.4.5, 1.5.1, 1.6.0 > > > When running CloudStone tests, I am prompted for ZKs, instead of being given the opportunity to specify them as a parameter, similar to user/password/instance. > Actually, looking at the code, there might be an option to specify them, but it is not enumerated in the README. -- This message was sent by Atlassian JIRA (v6.1.5#6160)