[
https://issues.apache.org/jira/browse/IMPALA-8284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785122#comment-16785122
]
Tim Armstrong commented on IMPALA-8284:
---------------------------------------
[~wdberkeley] Yes we could definitely cache it in Open(). It seems like the
author probably didn't realise that Column() was a heavyweight operation.
> KuduTableSink spends a lot of CPU copying KuduColumnSchemas
> -----------------------------------------------------------
>
> Key: IMPALA-8284
> URL: https://issues.apache.org/jira/browse/IMPALA-8284
> Project: IMPALA
> Issue Type: Improvement
> Affects Versions: Impala 3.1.0
> Reporter: Will Berkeley
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
