[jira] [Assigned] (IMPALA-8284) KuduTableSink spends a lot of CPU copying KuduColumnSchemas

["Todd Lipcon (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-8284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon reassigned IMPALA-8284:
-----------------------------------

    Assignee: Todd Lipcon

> 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
>          Components: Backend
>    Affects Versions: Impala 3.1.0
>            Reporter: Will Berkeley
>            Assignee: Todd Lipcon
>            Priority: Major
>              Labels: kudu, newbie, ramp-up
>
> 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: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org