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

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

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

Stefan Miklosovic updated CASSANDRA-18477:
------------------------------------------
     Bug Category: Parent values: Correctness(12982)
       Complexity: Normal
    Discovered By: Adhoc Test
    Fix Version/s: 5.x
         Severity: Low
         Assignee: Stefan Miklosovic
           Status: Open  (was: Triage Needed)

> Do not require allow filtering when all primary keys are specified in SELECT 
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18477
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18477
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL/Semantics
>            Reporter: Stefan Miklosovic
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>             Fix For: 5.x
>
>
> This was discussed in
> https://lists.apache.org/thread/loj6jgv54szdvyt3wmvbtwwrrg1dtlxq
> Basically, when I have this table:
> {code}
> create table ks.tb (p1 int, c1 int, col1 int, col2 int, primary key (p1, c1));
> {code}
> and I do this
> {code}
> select * from ks.tb where p1 = 1 and c1 = 2 and col2 = 1;
> {code}
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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