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-6160) Throw errror when attempting to create a secondary index against counter
Date Wed, 28 Jan 2015 20:02:36 GMT

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

Brandon Williams commented on CASSANDRA-6160:
---------------------------------------------

Actually, I don't think we should be allowing mixing counters in the same table, but go ahead
and make a new ticket [~nff] and [~slebresne] can decide.

> Throw errror when attempting to create a secondary index against counter
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6160
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6160
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>            Reporter: Adam Hattrell
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.2.11
>
>         Attachments: 6160.txt
>
>
> Using CQL you can create a secondary index against a counter which is then non-functional.
 
> {code}
> cqlsh:test> create table test2 (col1 int, col2 counter, primary key (col1)) ;
> cqlsh:test> create index dodgy on test2(col2) ;
> cqlsh:test> update test2 set col2 = col2 + 0 where col1 = 1 ;
> cqlsh:test> select * from test2 ;
>  col1 | col2
> ------+------
>     1 |    0
> cqlsh:t7088> select * from test2 where col2 = 0 ;
> {code}
> We should return an error to let users know they are in unsupported territory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message