You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2017/12/19 13:23:00 UTC
[jira] [Updated] (KUDU-2173) Partitions are pruned incorrectly when
range-partitioned on a PK prefix
[ https://issues.apache.org/jira/browse/KUDU-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated KUDU-2173:
------------------------------
Fix Version/s: 1.5.1
1.4.1
1.2.1
1.3.2
> 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
> Fix For: 1.3.2, 1.2.1, 1.4.1, 1.6.0, 1.5.1
>
>
> 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)