[
https://issues.apache.org/jira/browse/CASSANDRA-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971320#comment-14971320
]
Adam Holmberg commented on CASSANDRA-9813:
------------------------------------------
The driver presently models all columns in the metadata, regardless of whether
the should appear in generated CQL (whether that's right is debatable). cqlsh
uses the metadata model when writing the header. My recommendation would be to
instead use the column names from the results metadata. This will require an
addition to the driver API. If this approach sounds reasonable, I'll plan on
getting that update into the driver 3.0 ga, and we can follow up with the cqlsh
updates.
> cqlsh column header can be incorrect when no rows are returned
> --------------------------------------------------------------
>
> Key: CASSANDRA-9813
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9813
> Project: Cassandra
> Issue Type: Bug
> Reporter: Aleksey Yeschenko
> Labels: cqlsh
> Fix For: 3.x, 2.1.x, 2.2.x
>
> Attachments: Test-for-9813.txt
>
>
> Upon migration, we internally create a pair of surrogate clustering/regular
> columns for compact static tables. These shouldn't be exposed to the user.
> That is, for the table
> {code}
> CREATE TABLE bar (k int, c int, PRIMARY KEY (k)) WITH COMPACT STORAGE;
> {code}
> {{SELECT * FROM bar}} should not be returning this result set:
> {code}
> cqlsh:test> select * from bar;
> c | column1 | k | value
> ---+---------+---+-------
> (0 rows)
> {code}
> Should only contain the defined {{c}} and {{k}} columns.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
