[jira] [Created] (CASSANDRA-15500) only partition key push down when multiple cluster keys restricted in where clause

["onmstester (Jira)" <ji...@apache.org>]

onmstester created CASSANDRA-15500:
--------------------------------------

             Summary: only partition key push down when multiple cluster keys restricted in where clause
                 Key: CASSANDRA-15500
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15500
             Project: Cassandra
          Issue Type: Bug
            Reporter: onmstester


Using Apache Cassandra 3.11.2, defined a table like this:
 
_create table my_table(_
                 __                   _partition text,_
       __                   _clustering1 int,_
                  _clustering2 text,_
                  _data set<text>,_
                **                _*primary key (partition, clustering1, clustering2))*_
 
and configured slow queries threshold to 1ms in yaml to see how queries passed to cassandra. Query below:
 
_select * from my_table where partition='a' and clustering1= 1 and clustering2='b'_
 
would be like this in debug.log of cassandra:
 
_select * from my_table where partition='a' LIMIT 100>  (it means that the two cluster key restriction did not push down to storage engine and the whole partition been retrieved)_
 
but this query:
 
_select * from my_table where partition='a' and clustering1= 1_
 
_would be_
 
_select * from my_table where partition='a' and_ _clustering1= 1_ _LIMIT 100> (single cluster key been pushed down to storage engine)_
 
 
_So it seems to me that, we could not restrict multiple clustering keys in select because it would retrieve the whole partition ?!_



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org