[
https://issues.apache.org/jira/browse/CASSANDRA-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051254#comment-15051254
]
Adam Holmberg commented on CASSANDRA-9813:
------------------------------------------
bq. Was the comment made before we decided to not put CASSANDRA-10513 in 2.1 or
am I missing some part?
That's what happened.
I posted the original 2.1 patch here to get input before porting to later
branches. I've since heard differing opinions on what should go back to 2.1 for
cqlsh (CASSANDRA-10513 no, CASSANDRA-9302 yes). Seems like big new features
might go there, but fixes for minor, long standing bugs should not. If someone
has a proper heuristic I'd be glad to learn it.
I'll create a patch for 2.2+ regardless of any input on the above.
> 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: Adam Holmberg
> Labels: cqlsh
> Fix For: 2.1.x, 2.2.x, 3.x
>
> Attachments: 9813-2.1.txt, 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)
