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

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.2.0, 1.3.1, 1.4.0, 1.5.0
• Fix Version/s: 1.3.2, 1.2.1, 1.4.1, 1.6.0, 1.5.1
• Component/s: client
• Target Version/s: 1.6.0
• Code Review: https://gerrit.cloudera.org/#/c/8222/
• Assignee: Dan Burkert
• Reporter: Todd Lipcon
• Created: 05/Oct/17 23:41
• Updated: 19/Dec/17 13:22
• Resolved: 18/Dec/17 18:39

Description

Given a schema:

Schema [
  0:a[int8 NOT NULL],
  1:b[int8 NOT NULL]
]
PRIMARY KEY (a,b)

and a partition:

RANGE (a) PARTITION VALUES >= 10

... the partition pruner incorrectly handles the following scan spec:

 `a` < 11 AND `b` < 11

... and prunes the partition despite the possibility of it having a row like (10, 1)