[IMPALA-4439] Kudu DML should report the number of rows that could not be modified

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Kudu_Impala
• Fix Version/s: Impala 2.8.0
• Component/s: Backend
• Labels: kudu supportability
• Target Version: Impala 2.8.0
• Assignee: Matthew Jacobs
• Reporter: Matthew Jacobs
• Created: 07/Nov/16 17:29
• Updated: 30/Aug/18 18:48
• Resolved: 17/Nov/16 18:38

Description

Kudu DML operations ignore schema-related conflicts/violations (IMPALA-3710) because Kudu does not support multi-row transactions.

While the operations will report the number of rows modified through beeswax and the profile (unfortunately HS2 cannot return this information yet, see IMPALA-3713), the operations should also report the total number of rows that could not be modified. There are several reasons why rows might not be successfully modified, and a more detailed mechanism for reporting these errors is desirable but out of scope for now (that work is tracked by IMPALA-4416).

Issue Links

• is related to: IMPALA-3713 CRUD operations against Kudu tables should report the number of modified rows
• is related to: IMPALA-4445 Improve UPSERT NumRowsModified