[
https://issues.apache.org/jira/browse/CASSANDRA-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945179#comment-13945179
]
Sylvain Lebresne commented on CASSANDRA-6915:
---------------------------------------------
bq. I would argue that it's important to understand the storage layer
difference between PRIMARY KEY ((id, timestamp), event) and PRIMARY KEY (id,
timestamp, event)
It's important to understand what your partition key is, and that the partition
key decides how our table rows will be distributed on the cluster. But you
don't need to delve into "storage layer" representation to explain that. Again,
I think the approach of CASSANDRA-6910 of using separate colors in the
resultset header (colors that we could reuse in DESC) is simple and efficient.
> Show storage rows in cqlsh
> --------------------------
>
> Key: CASSANDRA-6915
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6915
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Robbie Strickland
> Labels: cqlsh
>
> In Cassandra it's super important to understand how your CQL schema
> translates to the underlying storage rows. Right now the only way to see
> this is to create the schema in cqlsh, write some data, then query it using
> the CLI. Obviously we don't want to be encouraging people to use the CLI
> when it's supposed to be deprecated. So I'd like to see a function in cqlsh
> to do this.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
