Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 28 Apr 2014 20:02:20 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12704353.1396035495995.193867.1398715340076@arcas>
In-Reply-To: <JIRA.12704353.1396035495995@arcas>
References: <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=13983473#comment-13983473 ] 

Sean Busbey commented on ACCUMULO-2589:
---------------------------------------

Could we use subclasses of RuntimeException to allow for both [~mdrob]'s ease of failing and [~vines]'s desired ability to catch and recover (without have to do the current insanity of parsing strings)?

> 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: 1.7.0
>
>
> 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.2#6252)