accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris McCubbin (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-482) Add a thrift proxy server
Date Wed, 07 Nov 2012 20:04:14 GMT


Chris McCubbin updated ACCUMULO-482:

    Status: Patch Available  (was: Open)

I'm submitting a first cut at this. It uses thrift and the proxy pretty much mirrors the capabilities
of the usual java connector, with a few caveats:

-Some of the methods aren't implemented, for various reasons.
-There's only one way to obtain a scanner, and one way to insert cells. Scanners still support
iterators, ranges, etc.

The thrift API file includes the accumulo data.thrift API and that file must be available
as a library when compiling the thrift. The compiled versions of the classes are included
in the patch, the same way that accumulo itself does.

The server is a standalone server for now, see the README. Example clients (with compiled
thrift classes) are included for Java, Python, and Ruby. For ruby and python I believe you
will have to install thrift for them to work. The java client (included in the maven project)
uses a maven thrift dependency so a thrift install is not needed. Another thing is that I
had a few dependency conflict issues with the main project so the proxy pom file does not
currently use the accumulo pom as a parent. The accumulo pom file still has proxy as a subproject
(e.g. it will install proxy when it is installed). I'm working to fix this.

Please test it out, let me know what you think. Thanks. --C
> Add a thrift proxy server
> -------------------------
>                 Key: ACCUMULO-482
>                 URL:
>             Project: Accumulo
>          Issue Type: New Feature
>            Reporter: Sapan Shah
>            Assignee: Chris McCubbin
> Add a thrift proxy server to make integration with other languages besides Java a bit
easier.  This should work like

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message