cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Dusbabek <>
Subject Re: State Of: CQL
Date Sun, 20 Mar 2011 12:29:33 GMT
Everybody is right.  The CQL<->SQL naming ambiguity is a problem.  We
need to do something about this before it gets out of hand.

I've been thinking about alternatives all weekend.  Here's one thing I
came up with that I think will do nicely.

Using our thrift API (the *old* way of doing things) had a tendency to
let low level API paradigms code seep and leak all over application
logic.  But we're not going to have that problem using CQL.  So I
thought "seepless" would be a good name because your data code would
stop seeping.

Then I realized that it didn't boil down to a cool acronym or even
have a symbol in it.  In grand fashion, I added a plus to the end of
seepless to arrive at "seepless+".  I think it has a nice ring and
will fit easily into Cassandra discussions:

"A great way to use Cassandra is write queries using seepless+."
"We've got seepless+ drivers for several languages including java and python."
"We're not using thrift anymore; we write all of our queries in seepless+ now."

Anyway, I'll keep thinking to see if I can come up with something
better.  I'm full of ideas this weekend.


On Fri, Mar 18, 2011 at 14:54, Eric Evans <> wrote:
> With 3 weeks and change until the branch-and-feature-freeze, I thought
> I'd take a few moments to update everyone on the current state of CQL.
> Goals and Progress[1]
> ---------------------
> The overarching goal of course, is to create a compelling replacement
> for the RPC interface, one that is less baroque, comparable in
> performance, and stable across Cassandra release versions.
> The goals for Cassandra 0.8 are to meet or exceed the point of minimum
> usability.  That is to say, a significant number of users/applications
> can make use of it.  I believe we're on track to achieve that.
> Already complete:
> * Complete data manipulation (SELECT, UPDATE, DELETE, TRUNCATE ...)
> * Partial DDL, enough to create a schema, (ALTER is missing).
> * Drivers for Python (including Twisted), and Java (JDBC).
> * Language documentation (doc/cql/CQL.html)
> Remaining for 0.8:
> * Support for typed keys[2].
> * Tests, tests, and more tests.
> What comes next (after 0.8)
> ---------------------------
> * Benchmarking and optimization
> * Completion of DDL (ALTER ...).
> * Prepared statements
> * Custom, line protocol (no more Thrift).
> * ... ?
> What you can do
> ---------------
> * Play/test/experiment, and file bug reports.  The Python driver's
> interactive interpreter is a good place to start (drivers/py/cqlsh).
> * Write system tests (test/system/
> * Write language drivers.
> * Write documentation.
> * Pick up unclaimed tickets tagged "cql"[3].
> * Port libraries and applications (and file bug reports).
> Thoughts, comments, questions?
> [1]:
> [2]:
> [3]:
> --
> Eric Evans

View raw message