cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4955) some confusion around KEY pseudocolumn from Thrift tables
Date Thu, 29 Nov 2012 19:42:58 GMT

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

Brandon Williams commented on CASSANDRA-4955:
---------------------------------------------

+1, this fixes the casing problem with the key (but CASSANDRA-4827 gets in the way now)
                
> some confusion around KEY pseudocolumn from Thrift tables
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-4955
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4955
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>             Fix For: 1.2.0 rc1
>
>         Attachments: 4955.txt
>
>
> Inserting into the schema created by cassandra-stress.  cqlsh {{DESCRIBE TABLE}} says
> {code}
> CREATE TABLE "Standard1" (
>   "KEY" blob PRIMARY KEY,
>   "C0" blob,
>   "C1" blob,
>   "C2" blob,
>   "C3" blob,
>   "C4" blob
> ) WITH COMPACT STORAGE AND
>   comment='' AND
>   caching='KEYS_ONLY' AND
>   read_repair_chance=0.100000 AND
>   dclocal_read_repair_chance=0.000000 AND
>   gc_grace_seconds=864000 AND
>   replicate_on_write='true';
> {code}
> but that casing doesn't actually work:
> {noformat}
> cqlsh:Keyspace1> insert into "Standard1" ("KEY", "C0", "C1", "C2", "C3", "C4") values
('FF', '00', '11', '22', '33', '44');
> Bad Request: Unknown identifier KEY
> {noformat}
> lowercase does work:
> {noformat}
> cqlsh:Keyspace1> insert into "Standard1" ("key", "C0", "C1", "C2", "C3", "C4") values
('FF', '00', '11', '22', '33', '44');
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message