For our current project we have decided to use Hector as the client API,
however, with the introduction of CQL I need to understand a few things.

Firstly, CQL use SQL like constructs. Column names seem to be limited to the
same constraints of SQL (restricted use of delimiters) and yet the strengths
of Cassandra actually lie in the fact that we can delimit column names for
hierarchical use - if anything it was encouraged at the Cassandra SF 2011
conference.

Should I be ensuring that I avoid using delimiters such as ':', '-' for
column names now?

Does CQL Support (Dynamic)Composite column names? Row Keys?

What other limitations does CQL have that are not present in Hector?

Thanks,
Anthony

Reply via email to