Thank you Eric,
I think we have a limited number of dynamically named columns but I'm
not inclined to have them added in the schema.
I have just managed to do what I want with the schema below. But It cost
me my secondary index on eventId. Because eventId is a clustering_key
it's not yet sup
I do not think that cqlsh provides a way to get internal data. I hope I am
wrong...
-Original Message-
From: Onur Yalazı [mailto:onur.yal...@8digits.com]
Sent: Thursday, October 15, 2015 10:54 AM
To: user@cassandra.apache.org
Subject: Accessing dynamic columns via cqlsh
Hello,
I have a
If the columns are not dynamically named (as in "actionId" and "code") you
should be able to add that to your CQL table definition with ALTER TABLE,
and those columns should be available in the query results.
If the columns *are* dynamically named, and you can't reasonably add every
option to the
Hello,
I have a cassandra cluster from pre-cql era and I am having problems
accessing data via cqlsh.
As you can see below, I can not reach dynamic columns via cqlsh but they
are accessible via cassandra-cli.
How can I make the data shown on cqlsh?
cqlsh:automation> select * from "EventKeys
