Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 26 Oct 2013 02:06:30 +0000 (UTC)
From: "John Vines (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12661448.1375469786805.6411.1382753190426@arcas>
In-Reply-To: <JIRA.12661448.1375469786805@arcas>
References: <JIRA.12661448.1375469786805@arcas>
Subject: [jira] [Updated] (ACCUMULO-1635) Support external configuration in
 client API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Vines updated ACCUMULO-1635:
---------------------------------

    Fix Version/s:     (was: 1.6.0)
                   1.7.0

> Support external configuration in client API
> --------------------------------------------
>
>                 Key: ACCUMULO-1635
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1635
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>             Fix For: 1.7.0
>
>
> Currently things like timeout, batch writer max mem, etc are only configurable in the API by making method calls.  It would be nice if a user could pass a config file to the connector that provides default configutations for things like timeout, batch writer max memory, etc.
> Since Accumulo is used on a cluster, in addition to a config file, supporting configuration profiles in zookeeper would also be nice.  For example I can tell my application to use configuration profile X in zookeeper.   If I do not specify a batch writer max mem, then it will look in the configuration profile in zookeeper.


--
This message was sent by Atlassian JIRA
(v6.1#6144)