YesQL is the only one that's made me laugh out loud so far. I'm a fan of that if we want to keep it light-hearted.
I think CassQL and Castle are both reasonable. 'seepless' has a great idea behind it, but it sounds a lot like like 'sleepless'. On Sun, Mar 20, 2011 at 11:06 AM, Jake Luciani <jak...@gmail.com> wrote: > I for one still like YesQL > > On Sun, Mar 20, 2011 at 8:29 AM, Gary Dusbabek <gdusba...@gmail.com> > wrote: > > > 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. > > > > Gary. > > > > > > On Fri, Mar 18, 2011 at 14:54, Eric Evans <eev...@rackspace.com> 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/test_cql.py). > > > * Write language drivers. > > > * Write documentation. > > > * Pick up unclaimed tickets tagged "cql"[3]. > > > * Port libraries and applications (and file bug reports). > > > > > > Thoughts, comments, questions? > > > > > > [1]: https://issues.apache.org/jira/browse/CASSANDRA-1703 > > > [2]: https://issues.apache.org/jira/browse/CASSANDRA-2311 > > > [3]: http://goo.gl/cSPlc > > > > > > -- > > > Eric Evans > > > eev...@rackspace.com > > > > > > > > > -- > http://twitter.com/tjake > -- Tyler Hobbs Software Engineer, DataStax <http://datastax.com/> Maintainer of the pycassa <http://github.com/pycassa/pycassa> Cassandra Python client library
