I was trying to mix CQL2 and CQL3 to check whether a columnfamily with
compound keys can be further indexed. Because using CQL3 secondary indexing
on table with composite PRIMARY KEY is not possible. And surprisingly by
mixing the CQL versions i was able to do so. But when i want to insert
CQL2 and CQL3 indexes are not compatible. I guess CQL2 is able to detect
that the table was defined in CQL3 probably should not allow it. Backwards
comparability is something the storage engines and interfaces have to
account for. At least they should prevent you from hurting yourself.
But do not
On Mon, Dec 10, 2012 at 12:36 PM, Abhijit Chanda
abhijit.chan...@gmail.comwrote:
Hi All,
I have a column family which structure is
CREATE TABLE practice (
id text,
name text,
addr text,
pin text,
PRIMARY KEY (id, name)
) WITH
comment='' AND
caching='KEYS_ONLY' AND
