[jira] [Updated] (CASSANDRA-10958) Range query with filtering interacts badly with static columns

["Sam Tunnicliffe (JIRA)" <ji...@apache.org>]

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

Sam Tunnicliffe updated CASSANDRA-10958:
----------------------------------------
    Summary: Range query with filtering interacts badly with static columns  (was: Range query using secondary index returns weird results)

Just to be clear, this isn't related to secondary indexes particularly. The same results are returned regardless of whether an index is defined or not. In fact, the index isn't being used when it is defined (hence the need to allow filtering), because the built in index implementations currently only support the equality operator. Rather, the issue seems to be that filtering seems to be somewhat broken in the presence of static columns.

> Range query with filtering interacts badly with static columns
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-10958
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10958
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Taiyuan Zhang
>            Priority: Minor
>
>  I'm playing with Cassandra 3. I added a secondary index on a column of integer, then I want to do a range query. First it threw an error:
> {code}
> InvalidRequest: code=2200 [Invalid query] message="No supported secondary index found for the non primary key columns restrictions"
> {code}
> So I added 'Allow Filtering'
> {code}
>     cqlsh:mykeyspace> SELECT * FROM test ;
>     id | id2 | age | extra
>     ----+-----+-----+-------
>       1 |   1 |   1 |     1
>       2 |   2 |   2 |     2
>     (2 rows)
>     cqlsh:mykeyspace > CREATE INDEX test_age on test (extra) ;
>     cqlsh:mykeyspace > select * FROM test WHERE extra < 2 ALLOW FILTERING ;
>      id | id2  | age | extra
>     ----+------+-----+-------
>       1 |    1 |   1 |     1
>       2 | null |   2 |  null
>     (2 rows)
> {code}
> My schema is:
> {code}
>     CREATE TABLE mykeyspace.test (
>     id int,
>     id2 int,
>     age int static,
>     extra int,
>     PRIMARY KEY (id, id2)
>     ) 
> {code}
> I don't know if this is by design or not, but it really does look like a BUG to me.



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