Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAPsZEyR7Tb=C0aod3F-M8ifjCX-fRDxn5XSngEHBpytYmyz3Dw@mail.gmail.com>
References: 
 <CAPsZEyR7Tb=C0aod3F-M8ifjCX-fRDxn5XSngEHBpytYmyz3Dw@mail.gmail.com>
Date: Wed, 2 May 2012 12:27:23 -0400
Message-ID: 
 <CAGUtCHoSdckeT_TJGpFt5S_J7FDNz-ztY=MeYcomAybyagtyvA@mail.gmail.com>
Subject: Re: Python client lib for Accumulo?
From: Keith Turner <keith@deenlo.com>
To: dev@accumulo.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, May 2, 2012 at 11:31 AM, Jason Trost <jason.trost@gmail.com> wrote:
> I noticed that there are no JIRAs for a python client
> interface/lib/API for Accumulo. =A0How involved would it be to develop
> AND maintain a python client for Accumulo?
>
> I realize that Jython can be used, but I am interested in a native
> python lib that can be use more broadly with systems that don't work
> with Jython.
>
> In order to do this, it seems like we would need to:
> 1. generate the python thrift bindings code (this is trivial)
> 2. develop and maintain the python glue code to use the thrift code
> and python zookeeper code to interact with the various accumulo
> components. =A0The current Java "glue" code looks quite long. =A0How ofte=
n
> does this code change (in terms of new features or changes in
> protocol, not bug fixes)?
>

I would advise against rewriting the accumulo client code in python.
The code that finds tablets, retries in case of failure, parallelizes
read/writes, etc is fairly complex.  I think the proxy option is best.
 David and Eric mentioned REST and Thrift proxies.

If we were to go to down the route of writing the client code in
another language, I think C++ with a C API would be the best option
because many language can easily bind to a C API.

> Ideally the python API would be very similar to the Java interface
> (Connector, Instance, Scanner, BatchScanner, BatchWriter, Key, Value,
> Mutation, etc).
>
> I guess what I am trying to get at is, does the Accumulo dev community
> think it's worth the time and effort to develop and maintain a python
> API? =A0I personally think it is in order to help with adoption and
> integration with other systems (Django is the primary system I want to
> be able to use with it). =A0I have some time to help this along, but I
> don't think I have enough time to take this on alone. =A0Is anyone else
> interested in working together on this?
>
> Thanks,
>
> --Jason