[IMPALA-5294] Kudu INSERT partitioning fails with constants

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Impala 2.9.0
• Fix Version/s: Impala 2.9.0
• Component/s: Frontend
• Labels: kudu
• Epic Color: ghx-label-9
• Assignee: Thomas Tauber-Marshall
• Reporter: Thomas Tauber-Marshall
• Created: 09/May/17 14:29
• Updated: 22/Jun/17 15:36
• Resolved: 11/May/17 17:16

Description

A recent change (IMPALA-3742) introduced a bug where INSERTs into Kudu table will fail with an IllegalStateException if they are inserting a constant value into a partition column and a non-constant value into another partition column.

The reason is that DistributedPlanner removed the constant exprs from the list of partition exprs before creating the KuduPartitionExpr, but the KuduPartitionExpr expects one expr for each partition column, and so a Precondition check is hit (unless all of the values inserted into partition cols are constant, then we fall back to an unpartitioned insert).

Issue Links

• is broken by: IMPALA-3742 INSERTs into Kudu tables should partition and sort