On Sun, 2011-03-20 at 22:11 +, Courtney Robinson wrote:
> I've been looking at the Java and Python drivers and they are both
> using Thrift. I thought the idea was to get rid of thrift/avro?
The idea is to create an alternative to the tightly-coupled
object-oriented RPC interface.
This initia
I've been looking at the Java and Python drivers and they are both using
Thrift. I thought the idea was to get rid of thrift/avro?
The two implemented (however partial) drivers seem to have similar naming
conventions for class and methods.
Has it been agreed to try and do this? I reckon it'd be
Possibly, I think doing a gsoc would leave a few dead projects and in the
end someone would decide to pick up one or two of them and possibly take
development in a diff. direction than was intended. Much like the multitude
of clients that start, die and get re-born.
---
I wonder if drivers for various languages could be google summer of code
projects. On the one hand it's a nice intro to cassandra and a discrete thing
to do. However, would that leave it maintainerless once gsoc was done...?
On Mar 20, 2011, at 11:42 AM, Tyler Hobbs wrote:
> YesQL is the only
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 wro
I for one still like YesQL
On Sun, Mar 20, 2011 at 8:29 AM, Gary Dusbabek 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
How about Prophecy? That was Cassandra's talent. For short it could be CPL
or PL. Cassandra Prophecy Language
On Mar 20, 2011 10:10 AM, "Jeremy Hanna" wrote:
I like Castle - sounds cool, though it mixes metaphors. Greek mythology and
medieval Europe... Still I think it's a cool name.
On Mar 20, 2011, at 7:44 AM, Andy Grundman wrote:
> Cassandra Interface Language == CassIL == "Castle" ?
>
> On Mar 20, 2011, at 8:35 AM, Andy Twigg wrote:
>
>> SQL
Conservatively and true to the initial name:
CassQL => Cassandra Query Language
A bit more left-field:
CQ => Cassandra Query
CL => Cassandra Language
I'm partial to CQ myself, as it:
* Suggests a verb - "seek".
* Has geeky secondary [but highly relevant] meaning:
http://en.wikipedia.org/wiki/
Cassandra Interface Language == CassIL == "Castle" ?
On Mar 20, 2011, at 8:35 AM, Andy Twigg wrote:
> SQL = "structured query language", so (since cassandra is partially about
> unstructured data), what about "unstructured query language" = UQL ?
>
>
> On 20 March 2011 12:29, Gary Dusbabek wro
SQL = "structured query language", so (since cassandra is partially about
unstructured data), what about "unstructured query language" = UQL ?
On 20 March 2011 12:29, Gary Dusbabek wrote:
> Everybody is right. The CQL<->SQL naming ambiguity is a problem. We
> need to do something about this b
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) h
There was some opposition to the name CQL due to name conflicts.
May I suggest "Cassquel"? I think it has a nice sound.
On Fri, Mar 18, 2011 at 9:54 PM, 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 th
13 matches
Mail list logo
