[
https://issues.apache.org/jira/browse/CASSANDRA-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630154#comment-14630154
]
Aleksey Yeschenko commented on CASSANDRA-9813:
----------------------------------------------
The particular issue I described is caused by python-driver not handling the
post-8099 column metadata yet. Doesn't depend on CASSANDRA-6717, but something
to be fixed by
[PYTHON-276|https://datastax-oss.atlassian.net/browse/PYTHON-276]. If the right
columns are exposed by the driver, then even an empty result should show valid
metadata for {{SELECT *}} queries.
> 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
> Assignee: Sylvain Lebresne
> 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)
