[jira] [Commented] (KUDU-2173) Partitions are pruned incorrectly when range-partitioned on a PK prefix

["Todd Lipcon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193928#comment-16193928 ] 

Todd Lipcon commented on KUDU-2173:
-----------------------------------

The reason we missed this bug is that partition_pruner-test wasn't calling OptimizeScanSpec and thus didn't produce the same behavior as the client. Repro test code here: https://gist.github.com/24f8bcb78187a18c91e04c6c36d165a2


> Partitions are pruned incorrectly when range-partitioned on a PK prefix
> -----------------------------------------------------------------------
>
>                 Key: KUDU-2173
>                 URL: https://issues.apache.org/jira/browse/KUDU-2173
>             Project: Kudu
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.2.0, 1.3.1, 1.4.0, 1.5.0
>            Reporter: Todd Lipcon
>            Assignee: Dan Burkert
>            Priority: Blocker
>
> Given a schema:
> {code}
> Schema [
>   0:a[int8 NOT NULL],
>   1:b[int8 NOT NULL]
> ]
> PRIMARY KEY (a,b)
> {code}
> and a partition:
> {code}
> RANGE (a) PARTITION VALUES >= 10
> {code}
> ... the partition pruner incorrectly handles the following scan spec:
> {code}
>  `a` < 11 AND `b` < 11
> {code}
> ... and prunes the partition despite the possibility of it having a row like (10, 1)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)