Hi Paul,

many thanks for your informative answer! It's very exciting to see all those new
and upcoming features in Cassandra.

>> 3) Stability
> Ouch, that's pretty bad. File a jira ticket for that, for sure. The binary
> protocol will still be "beta" for the 1.2 release, and not enabled by
> default, so it's not earth-stopping, but I'm sure we want it more stable
> than THAT.

I will try to collect some test cases that have caused that kind of bad
behavior during the following week. I will submit a ticket once I have
more details available.

>> 4. Prepared Statements
> Agreed. I remember hearing about this happening with the thrift interface
> too -
> http://code.google.com/a/apache-extras.org/p/cassandra-dbapi2/issues/detail?id=21&can=1came
> from there- but it doesn't look like anyone bothered to file a jira
> ticket. Want to do that one too?

Ticket+Patch: https://issues.apache.org/jira/browse/CASSANDRA-4577

---

I will continue asking some questions here in this thread instead of creating a
new one every time. I guess most of my questions are answered quickly anyway.

5) LIMIT

The last query with LIMIT 1 in this example returns a very strange result imho.
Instead of just limiting the rows, it also replaces most column values
with NULL.
Is this the expected behavior? https://gist.github.com/3483042

> Best of luck with progress!

Thank you. You can track my progress here if you are interested:
https://github.com/tux21b/gocql

Regards,
Christoph

Reply via email to