Samrat Gandotra created CASSANDRA-13599:
-------------------------------------------
Summary: Filtering on Secondary Index throws out of memory error
even with limit 1 and mentioning the partition key in the where clause.
Key: CASSANDRA-13599
URL: https://issues.apache.org/jira/browse/CASSANDRA-13599
Project: Cassandra
Issue Type: Bug
Environment: Using Cassandra 3.10 on Windows 7
Reporter: Samrat Gandotra
We have used secondary index on a column with very low cardinality.
So if we use partition key and any secondary index value ( value which has
millions of corresponding rows in the table) in the where clause with limit 1
even then it takes lot of time to respond and atlast out of memory error occurs.
The correct scenario should be that if we are mentioning a very small limit
like 1 then the results should be shown immediately when the secondary index
and partition key is used in the where clause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
