Some of you might already be aware, but I recently proposed a query
language as an alternative to (or full replacement for) the Thrift/Avro
RPC interfaces.
http://article.gmane.org/gmane.comp.db.cassandra.devel/2370
For me, this isn't so much about making the raw Cassandra interface
easier, as
On Thu, 2010-11-04 at 09:30 -0700, Dave Viner wrote:
1. How does replacing thrift/avro with a SQL-inspired query language make
the server more stable? As a client, I still need to connect via something,
and that something will make something like an RPC call to the server. In
traditional
A QL can shield clients from a class of changes, but OTOH will make clients
have to compose the query strings, where with type safe libraries this job
is somewhat easier. IMO in the near term introducing a query language will
make client dev somewhat harder b/c of the (somewhat negligible) work of
On Thu, Nov 4, 2010 at 1:44 PM, Jonathan Ellis jbel...@gmail.com wrote:
Apparently Eric has become a fan of Android-style release names.
Actually, I replaced HH with chocolate pudding cake. It's not any more
useful, but it tastes better.
-Brandon
On Thu, 2010-11-04 at 13:41 -0500, Nate McCall wrote:
Fyi: #1 looks like a pretty good chocolate brownie recipe. Is that
Google's fault or a typo? (either way, thanks!).
Ha! Awesome. I need to start doing that on purpose from time to time.
FWIW, it should have been: http://goo.gl/pGEx5
On
On Thu, 2010-11-04 at 21:28 +0200, Ran Tavory wrote:
A QL can shield clients from a class of changes, but OTOH will make
clients have to compose the query strings, where with type safe
libraries this job is somewhat easier. IMO in the near term
introducing a query language will make client dev
