>> a2 | a2c1 | a2c2
>> a1 | a1c1 | a1c2
>>
>> This comes with many important restrictions, one of which as mentioned is
>> that you cannot have arbitrary columns in a CQL3 table, just like you
>> cannot in a traditional relational database. Likewise you
I run a 1.1 cluster and currently testing out a 1.2 cluster. I have
noticed that with 1.2 it switched to CQL3 which is acting differently than
I would expect. When I do "select key from \"cf\";" I get many many
duplicate keys. When I did the same with CQL 2 I only get the keys
defined. This see
