Re: Cassandra 1.2 compatible Python bindings

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 COMPACT STORAGE seems to be really the issue why I can not see my table using pycassa. Unfortunately COMPACT STORAGE does not seem to support collection types *sigh*. - -aj aaron morton wrote: >> I know work is in progress to fix this... > AFAIK CF's

Questions about the binary protocol spec.

I'm working on a C++ driver for the new binary protocol, and have one or two items of feedback/questions regarding the spec. 1. There are column types that correspond to types that are not defined by the spec such as Boolean, UUID, Timestamp, Decimal, Double, Float etc.. Will these types always a

Re: Cassandra 1.2 compatible Python bindings

I have a C++ driver that is nearly complete for the new binary protocol, and I plan on creating wrappers for python and ruby. Was going to announce next week hopefully. It needs some more unit tests and docs. It also currently lacks connection pooling and retry. https://github.com/mstump/libcql

Re: Cassandra 1.2 compatible Python bindings

This is perhaps my issue :-) Thanks for the pointer with COMPACT STORAGE. Andreas aaron morton wrote: >> I know work is in progress to fix this... > AFAIK CF's created by CQL 3 using COMPACT STORAGE are visible to > thrift. Those created without it are not, and will not, be visible to > thrift.

Re: Cassandra 1.2 compatible Python bindings

> I know work is in progress to fix this... AFAIK CF's created by CQL 3 using COMPACT STORAGE are visible to thrift. Those created without it are not, and will not, be visible to thrift. Cheers - Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.the

Re: Column Family migration/tombstones

> Are there other performance considerations that I need to keep in mind? Thats about it. Sylvain has written a script or some such to reverse compaction. It was mentioned sometime in the last month I think. Sylvain ? > after we are complete the migration should be fairly small (about 500,000

Re: Cassandra 1.2 compatible Python bindings

I know one outstanding issue is that CQL3 created column families won't be listed as CQL3 column families aren't exposed by the old thrift calls. I know work is in progress to fix this... On Jan 6, 2013, at 8:01 PM, "aaron morton" mailto:aa...@thelastpickle.com>> wrote: I'm not aware of any is

Re: Cassandra 1.2 compatible Python bindings

I'm not aware of any issues with using the thrift API with http://pycassa.github.com/pycassa/ and 1.2 Cheers - Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 7/01/2013, at 8:21 AM, Adam Venturella wrote: > I have been using

Re: Schema recommendation

> - basically the task is to create a distributed file system with only few > allowed operations Background http://www.datastax.com/dev/blog/cassandra-file-system-design > - it should handle split brain conditions well (two or three DCs, it's > possible to get user requests while the intra-DC co

Re: system.peers.tokens is empty after node restart

Curious... What does nodetool ring say in this state? I assume each node only lists itself in the ring? On Jan 6, 2013, at 2:35 PM, "Pierre Chalamet" mailto:pie...@chalamet.net>> wrote: Hello, Using a 2 nodes fresh cluster (127.0.0.1 & 127.0.0.2) running latest 1.2, I’m querying system.peers

Re: Column Family migration/tombstones

Thanks Aaron, I appreciate it. It is my understanding, major compactions are not recommended because it will essentially create one massive SSTable that will not compact with any new SSTables for some time. I can see how this might be a performance concern in the general case, because any rea

system.peers.tokens is empty after node restart

Hello, Using a 2 nodes fresh cluster (127.0.0.1 & 127.0.0.2) running latest 1.2, I'm querying system.peers to get the nodes of the cluster and their respective token. But it seems there is a problem after either node restart. When both node starts up, querying system.peers seems ok: 127

Re: Column Family migration/tombstones

> When these rows are deleted, tombstones will be created and stored in more > recent sstables. Upon compaction of sstables, and after gc_grace_period, I > presume cassandra will have removed all traces of that row from disk. Yes. When using Size Tiered compaction (the default) tombstones are pu

Re: Cassandra 1.2 compatible Python bindings

I have been using this successfully so far: http://pypi.python.org/pypi/cql On Sun, Jan 6, 2013 at 11:18 AM, Andreas Jung wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Are there any up-to-date Python bindings available that > work with Cassandra 1.2? > > - -aj > -BEGIN PGP S

Cassandra 1.2 compatible Python bindings

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Are there any up-to-date Python bindings available that work with Cassandra 1.2? - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJQ6c3zAAoJEADcfz7u4AZjV

Schema recommendation

Hi, I'm new to Cassandra, so I wonder what would be the most efficient(*) schema for specific operations on the following dataset: - basically the task is to create a distributed file system with only few allowed operations - it should handle split brain conditions well (two or three DCs, it's