You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2015/07/16 13:15:05 UTC

[jira] [Updated] (CASSANDRA-9813) Surrogate columns are being exposed via CQL for compact static tables

     [ https://issues.apache.org/jira/browse/CASSANDRA-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne updated CASSANDRA-9813:
----------------------------------------
    Attachment: Test-for-9813.txt

Are we sure this is not a driver/cqlsh issue? I wrote a simple test (attached) that checks the metadata generated for the {{SELECT}} of your example above, and unless I've done something wrong in the test, only {{c}} and {{k}} are included in the response metadata.

I know next to nothing of the python driver and cqlsh implementations, but it would be possible that one of those is using the metadata from its reading of the schema rather than the response schema (that the surrogate columns are part of the schema table is a necessity and it's probably the driver that will need fixing on that front, though that probably mostly depend on CASSANDRA-6717 in practice). Could someone with more knowledge of the python driver/cqlsh confirm is the hypothesis above is plausible?

> Surrogate columns are being exposed via CQL for compact static tables
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-9813
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9813
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Sylvain Lebresne
>             Fix For: 3.0 beta 1
>
>         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)