cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9813) cqlsh column header can be incorrect when no rows are returned
Date Thu, 10 Dec 2015 18:02:11 GMT

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

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

How will this change work for people running an older version of the python driver? If it
requires people to upgrade to work it seems to me we should only do it for the next release?

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

Mime
View raw message