[IMPALA-8284] KuduTableSink spends a lot of CPU copying KuduColumnSchemas

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 3.1.0
• Fix Version/s: Impala 3.3.0
• Component/s: Backend
• Labels: kudu newbie ramp-up
• Epic Color: ghx-label-8
• Assignee: Todd Lipcon
• Reporter: William Berkeley
• Created: 05/Mar/19 23:00
• Updated: 18/Mar/19 09:15
• Resolved: 08/Mar/19 21:16

Description

I noticed Impala spending a significant amount of CPU time in KuduTableSink::Send creating and destroying KuduColumnSchemas.

See KUDU-2731 for more information.

Impala could wait for a better option from the Kudu API, or could cache information about nullability of columns outside the hot loop in Send.

Issue Links

• relates to: KUDU-2731 Getting column schema information from KuduSchema requires copying a KuduColumnSchema object