You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2019/03/05 23:01:00 UTC

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

Will Berkeley created IMPALA-8284:
-------------------------------------

             Summary: 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


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