I need to look at the Hive storage handler Henry but I imagine that the motivation and implementation is and would be similar in principle. With regards to your second point, this is very true and it is not going to be a simple thing to achieve. The thing which is working on our side is that Gora is still a young project at heart. We're still actively finding new improvements, suggestions to improve the core API etc. For example, we don't even support delete or deleteByQuery in gora-cassandra TODO ;)
Our motivation is really to discover what degree of overhead Gora put on operations between user and Datastore. In.Cassandra there are many possible clients we could build on e.g. hector client, datastax java driver, intravert-ug etc so we want to find this stuff out if we are.to make the best code available. On Monday, March 4, 2013, Henry Saputra <[email protected]> wrote: > Would this similar to storage handler architecture approach in Hive? > Looks like good idea. > The problem/difficulty I could think of on the top of my head is the vast differences between operations in the origin data sources. So the API has to be very generic and at the same time complete to cover all scenarios. > - Henry > > On Tue, Feb 26, 2013 at 3:55 PM, Lewis John Mcgibbney < [email protected]> wrote: >> >> Hi, >> Me and Renato are only discussing a pluggable client architecture for Gora. >> The motivation to discuss pluggable clients is performance across Gora and the fact that so far we (between Renato and Myself) have little or no indication of how the current performance is within Gora. >> To put this into context, if one were to consider the gora-cassandra module you see that we utilize Hector client as the underlying access Apache Cassandra. We are interested to find if there are benefits (for Gora) to be leveraged from comparing performance of clients. >> Is there any comments on this from anyone? >> Thank you >> Lewis >> >> -- >> Lewis > > -- *Lewis*
