accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2589) Create new client API
Date Mon, 16 Jun 2014 22:48:02 GMT

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

Josh Elser commented on ACCUMULO-2589:
--------------------------------------

Depending on the route that ACCUMULO-2915 takes to avoid extra copying of Mutations, it might
be prudent to consider if the BatchWriter API itself requires some re-thinking.

> 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)

Mime
View raw message