Welcome Edmon. I think as far as a pure python library goes, you would have to interface with the thrift protocols. My sense is that would be discouraged at this point by the devs. I do have some experience with it though, I made an attempt to interface to Accumulo with Node.js. It turned into me writing the JavaScript version of TCompactProtocol, but it's still incomplete at this point. I would vote for either developing an officially supported Thrift interface, or an officially supported REST interface using a JVM language. Then the language barrier would be easier to overcome.
Jim On Jul 27, 2012, at 7:19 AM, Edmon Begoli <[email protected]> wrote: > Hi David, > > I think that Jython is a good idea as at least a prototype or as a bridge > towards a full blown python library. > > It is probably not a good end state because most Python developers do not > want JVM and Java environment, and there is also performance overhead. > > Personally, I program in both languages, so I am good. > > Is there a particular protocol about contributing to accumulo project? > On Jul 27, 2012 5:27 AM, "David Medinets" <[email protected]> wrote: > >> On Thu, Jul 26, 2012 at 11:15 PM, Edmon Begoli <[email protected]> wrote: >>> I have just joined the list with the purpose of volunteering ideas, >>> design and development (and whatever else in lifecycle) >>> related to development of the Python client for accumulo. >> >> Welcome to the list. There are a lot of Python developers and I'm sure >> that your client would be well received by the community. My own >> advice is to write whatever is simplest (fastest to develop) and >> iterate towards a more complex complete solution. >> >> Would jython be any use to provide python access to the existing Java >> API without any rewrite or plumbing needed? >>
