[CASSANDRA-13599] Filtering on Secondary Index throws out of memory error even with limit 1 and mentioning the partition key in the where clause.

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Component/s: Feature/2i Index

Environment

Using Cassandra 3.10 on Windows 7

• Severity: Normal
• Assignee: Unassigned
• Reporter: Samrat Gandotra
• Created: 14/Jun/17 06:17
• Updated: 16/Apr/19 09:30

Description

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.