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

Hannu Kröger updated CASSANDRA-13228:
-------------------------------------
    Description: 
I created a SASI index on first part of multi-part partition key. Running query 
using that index doesn't seem to work.

I have here a log of queries that should indicate the issue:

{code}cqlsh:test> CREATE TABLE test1(name text, event_date date, data_type 
text, bytes int, PRIMARY KEY ((name, event_date), data_type));
cqlsh:test> CREATE CUSTOM INDEX test_index ON test1(name) USING 
'org.apache.cassandra.index.sasi.SASIIndex';
cqlsh:test> INSERT INTO test1(name, event_date, data_type, bytes) 
values('1234', '2010-01-01', 'sensor', 128);
cqlsh:test> INSERT INTO test1(name, event_date, data_type, bytes) 
values('abcd', '2010-01-02', 'sensor', 500);
cqlsh:test> select * from test1 where NAME = '1234';

 name | event_date | data_type | bytes
------+------------+-----------+-------

(0 rows)
cqlsh:test> CONSISTENCY ALL;
Consistency level set to ALL.
cqlsh:test> select * from test1 where NAME = '1234';

 name | event_date | data_type | bytes
------+------------+-----------+-------

(0 rows){code}

Note! Creating a SASI index on single part partition key, SASI index creation 
fails. Apparently this should not work at all, so is it about missing 
validation on index creation?

  was:
I created a SASI index on first part of multi-part partition key. Running query 
using that index doesn't seem to work.

I have here a log of queries that should indicate the issue:

{code}cqlsh:test> CREATE TABLE test1(name text, event_date date, data_type 
text, bytes int, PRIMARY KEY ((name, event_date), data_type));
cqlsh:test> CREATE CUSTOM INDEX test_index ON test1(name) USING 
'org.apache.cassandra.index.sasi.SASIIndex';
cqlsh:test> INSERT INTO test1(name, event_date, data_type, bytes) 
values('1234', '2010-01-01', 'sensor', 128);
cqlsh:test> INSERT INTO test1(name, event_date, data_type, bytes) 
values('abcd', '2010-01-02', 'sensor', 500);
cqlsh:test> select * from test1 where NAME = '1234';

 name | event_date | data_type | bytes
------+------------+-----------+-------

(0 rows)
cqlsh:test> CONSISTENCY ALL;
Consistency level set to ALL.
cqlsh:test> select * from test1 where NAME = '1234';

 name | event_date | data_type | bytes
------+------------+-----------+-------

(0 rows){code}

Note1 Creating a SASI index on single part partition key, SASI index creation 
fails. Apparently this should not work at all, so is it about missing 
validation on index creation?


> SASI index on partition key part doesn't match
> ----------------------------------------------
>
>                 Key: CASSANDRA-13228
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13228
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Hannu Kröger
>
> I created a SASI index on first part of multi-part partition key. Running 
> query using that index doesn't seem to work.
> I have here a log of queries that should indicate the issue:
> {code}cqlsh:test> CREATE TABLE test1(name text, event_date date, data_type 
> text, bytes int, PRIMARY KEY ((name, event_date), data_type));
> cqlsh:test> CREATE CUSTOM INDEX test_index ON test1(name) USING 
> 'org.apache.cassandra.index.sasi.SASIIndex';
> cqlsh:test> INSERT INTO test1(name, event_date, data_type, bytes) 
> values('1234', '2010-01-01', 'sensor', 128);
> cqlsh:test> INSERT INTO test1(name, event_date, data_type, bytes) 
> values('abcd', '2010-01-02', 'sensor', 500);
> cqlsh:test> select * from test1 where NAME = '1234';
>  name | event_date | data_type | bytes
> ------+------------+-----------+-------
> (0 rows)
> cqlsh:test> CONSISTENCY ALL;
> Consistency level set to ALL.
> cqlsh:test> select * from test1 where NAME = '1234';
>  name | event_date | data_type | bytes
> ------+------------+-----------+-------
> (0 rows){code}
> Note! Creating a SASI index on single part partition key, SASI index creation 
> fails. Apparently this should not work at all, so is it about missing 
> validation on index creation?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to