Except for any server side iterator logic, table balancers, etc...
----- Original Message ----- From: "Jonathan Parise" <[email protected]> To: [email protected] Sent: Wednesday, July 29, 2015 3:02:27 PM Subject: RE: Question regarding java being the choice for accumulo I’m not sure what the motivation behind the question is, but one other thing to keep in mind is that you can write you own program in whatever language you want and still use Accumulo. Accumulo uses Apache Thrift, so you can use whatever language you want with Accumulo. You just need to compile the thrift code to your language of choice. Thrift will give you an Accumulo API in that language. So if you really want to write you code in C++, you can do that and still use Accumulo. You will need a JVM to run Accumulo itself, but your code won’t need to be java based. Jon From: vaibhav thapliyal [mailto:[email protected]] Sent: Wednesday, July 29, 2015 2:24 PM To: [email protected] Subject: Re: Question regarding java being the choice for accumulo Thank you Josh and Keith. Vaibhav On 29-Jul-2015 11:44 pm, "Keith Turner" < [email protected] > wrote: We have a small amount of C++ code used to manage all data written to Accumulo. Using C++ for this very small amount of high performance, memory intensive code has worked out well. Coding task that do not need to be high performance in Java, like tablet assignment and management of cluster state is nice. On Wed, Jul 29, 2015 at 1:51 PM, vaibhav thapliyal < [email protected] > wrote: Hello everyone, I was wondering why did the developers chose java for writing accumulo. What advantage it has over using any other language say C++(in which another popular nosql database MongoDB is written) in context of accumulo? Thanks Vaibhav
