[ https://issues.apache.org/jira/browse/CASSANDRA-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051227#comment-15051227 ]
Sylvain Lebresne commented on CASSANDRA-9813: --------------------------------------------- This is marked "ready to commit", but I'm a tad confused. The patch says it's for 2.1, but an earlier comment says it's based on CASSANDRA-10513 which is 2.2 only. Was the comment made before we decided to not put CASSANDRA-10513 in 2.1 or am I missing some part? If that should only go in 2.2 (which btw I think is reasonable since that's in no way critical for 2.1), then can we get a rebased patch for that and run some CI on it before we call it ready to commit? > 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)