You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ariel Weisberg (JIRA)" <ji...@apache.org> on 2015/12/07 22:30:11 UTC

[jira] [Commented] (CASSANDRA-9813) cqlsh column header can be incorrect when no rows are returned

    [ https://issues.apache.org/jira/browse/CASSANDRA-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045773#comment-15045773 ] 

Ariel Weisberg commented on CASSANDRA-9813:
-------------------------------------------

I am very confused as to why I didn't see this in my search filter and respond faster. I apologize.

+1

> 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: 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)