[CASSANDRA-18477] Do not require allow filtering when all primary keys are specified in SELECT

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.x
• Component/s: CQL/Semantics
• Bug Category: Correctness
• Severity: Low
• Complexity: Normal
• Discovered By: Adhoc Test
• Platform: All

Test and Documentation Plan

ci

• Assignee: Stefan Miklosovic
• Reporter: Stefan Miklosovic

Authors

Stefan Miklosovic

• Created: 24/Apr/23 11:19
• Updated: 24/Apr/23 11:28
• Resolved: 24/Apr/23 11:28

Description

This was discussed in

https://lists.apache.org/thread/loj6jgv54szdvyt3wmvbtwwrrg1dtlxq

Basically, when I have this table:

create table ks.tb (p1 int, c1 int, col1 int, col2 int, primary key (p1, c1));

and I do this

select * from ks.tb where p1 = 1 and c1 = 2 and col2 = 1;

this will fail and it will require to use ALLOW FILTERING just because we are also specifying "col2". This is clearly a bug - there is no reason to require it if we are going to fetch one row only as all partition and clustering keys were specified.

Issue Links

• duplicates: CASSANDRA-15803 Separate out allow filtering scanning through a partition versus scanning over the table
• links to: GitHub Pull Request #2293