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 8711311412 for ; Fri, 19 Sep 2014 17:07:45 +0000 (UTC) Received: (qmail 40597 invoked by uid 500); 19 Sep 2014 17:07:45 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 40560 invoked by uid 500); 19 Sep 2014 17:07:45 -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 40443 invoked by uid 99); 19 Sep 2014 17:07:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 17:07:45 +0000 Date: Fri, 19 Sep 2014 17:07:45 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-2189) Document the Repo interface 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-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated ACCUMULO-2189: --------------------------------- Fix Version/s: (was: 1.5.2) 1.5.3 > Document the Repo interface > --------------------------- > > Key: ACCUMULO-2189 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2189 > Project: Accumulo > Issue Type: Sub-task > Components: docs, fate > Reporter: Vikram Srivastava > Fix For: 1.5.3, 1.6.1, 1.7.0 > > > The Repo interface is lacking java doc. For example: > Repo.isReady return a long and there is no documentation about what its return value should be and how it is used. > Currently it's used by Fate.run to decide whether to run "Repo.call" or not. If that's the only purpose it is used for, then isReady should return a boolean. If we do want it to return a long, then we should at least use constants by the various derived classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)