Unfortunately, no. I've read that and the solution presented only works in limited scenarios. Using the post's example, consider the query of "get all readings for sensor 1". With dynamic columns, the query is just "select * from data where sensor_id=1". In CQL, not only does this take N different queries (one per sample) but you have to explicitly know the collected_at values to query for. Right?
The other suggestion, to use collections (such as a map), again works in some circumstances, but not all. In particular, each item in a collection is limited to 64k bytes which is not something we want to be limited to (we are storing byte arrays that occasionally exceed this size). On Tue, Aug 26, 2014 at 3:14 PM, Shane Hansen <shanemhan...@gmail.com> wrote: > Does this answer your question Ian? > http://www.datastax.com/dev/blog/does-cql-support-dynamic-columns-wide-rows > > > > On Tue, Aug 26, 2014 at 1:12 PM, Ian Rose <ianr...@fullstory.com> wrote: > >> Is it possible in CQL to create a table that supports dynamic column >> names? I am using C* v2.0.9, which I assume implies CQL version 3. >> >> This page appears to show that this was supported in CQL 2 with the 'with >> comparator' and 'with default_validation' options but that CQL 3 does not >> support this: http://www.datastax.com/dev/blog/whats-new-in-cql-3-0 >> >> Am I understanding that right? If so, what is my best course of action? >> Create the table using the cassandra-cli tool? >> >> Thanks, >> - Ian >> >> >
