Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 30 Apr 2015 03:34:06 +0000 (UTC)
From: "William Slacum (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12704353.1396035495000.30620.1430364846510@Atlassian.JIRA>
In-Reply-To: <JIRA.12704353.1396035495000@Atlassian.JIRA>
References: <JIRA.12704353.1396035495000@Atlassian.JIRA>
 <JIRA.12704353.1396035495995@arcas>
Subject: [jira] [Commented] (ACCUMULO-2589) Create new client API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520792#comment-14520792 ] 

William Slacum commented on ACCUMULO-2589:
------------------------------------------

For anything like buffer sizes or timeouts (anything with a unit), I've been using the [Amount|http://twitter.github.io/commons/apidocs/index.html#com.twitter.common.quantity.Amount] class from [twitter commons|http://twitter.github.io/commons/]. Being able to specify units as part of the type (ie, {{Amount<Long, Time.Milliseconds> timeout}} vs {{long timeoutMS}}) has been a huge win. I'd be nice to use that when doing something like configuring a batch writer.

> Create new client API
> ---------------------
>
>                 Key: ACCUMULO-2589
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2589
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: client
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>            Priority: Blocker
>             Fix For: 2.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are many issues with the current client API, and we've had a lot of lessons learned that could be incorporated into a new one.
> Some of the issues this would address:
> * questions like "What is considered 'Public API'?"
> * automated testing for incompatible API changes
> * provide better support for alternative implementations of pluggable features
> * distinguish between compile-time dependencies and runtime dependencies
> * consistent exception handling
> * consistent/symmetric getters/setters
> * well-defined resource lifecycles
> * better resource management
> * simpler entry point to communicate with Accumulo
> * better support for client-side configuration management
> * logical layout of first class Accumulo objects in the API (Table, User, Scan, Connection)
> Some of these goal may evolve during the development of this feature, and many previously identified issues can be moved to sub-tasks of this one. This ticket is intended to cover the overall feature, but the details will be handled in sub-tasks.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)