cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-5018) Some queries with collections require quoting the key even when the key is an integer
Date Tue, 04 Dec 2012 13:57:00 GMT

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

Sylvain Lebresne resolved CASSANDRA-5018.
-----------------------------------------

    Resolution: Duplicate

Marking this a duplicate of CASSANDRA-5017 because the 2nd patch attached to that issue happens
to fix this issue too.
                
> Some queries with collections require quoting the key even when the key is an integer
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5018
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5018
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0 beta 2
>            Reporter: Aleksey Yeschenko
>            Assignee: Sylvain Lebresne
>            Priority: Trivial
>
> collections (id int primary key, amap map<int, varchar>);
> "UPDATE test.collections SET amap[1] = 'text' WHERE id = 0" -> List operations are
only supported on List typed columns
> "UPDATE test.collections SET amap['1'] = 'text' WHERE id = 0" -> ok
> Not sure if boolean/double/uuid/etc. are affected or require quoting as well.
> DELETE is not affected though: "DELETE amap[1] from test.collections where id = 0" ->
ok

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