You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Alexey Serbin (JIRA)" <ji...@apache.org> on 2018/08/21 21:41:00 UTC

[jira] [Created] (KUDU-2547) Add timing debug logs to KuduContext.writePartitionRows

Alexey Serbin created KUDU-2547:
-----------------------------------

             Summary: Add timing debug logs to KuduContext.writePartitionRows 
                 Key: KUDU-2547
                 URL: https://issues.apache.org/jira/browse/KUDU-2547
             Project: Kudu
          Issue Type: Improvement
          Components: client, spark
            Reporter: Alexey Serbin


It would be nice to add some timing debug logs into {{KuduContext.writePartitionRows}} to allow for easier troubleshooting of timing and performance issues.

The rationale is that when the {{writePartitionRows}} runs we know the source data is fully materialized and filters have been applied, etc.  which helps to deal with uncertainty of lazy evaluation in Scala/Spark applications.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)