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 "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/10/05 01:00:00 UTC

[jira] [Commented] (IMPALA-7652) Fix BytesRead for Kudu scans

    [ https://issues.apache.org/jira/browse/IMPALA-7652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639112#comment-16639112 ] 

Tim Armstrong commented on IMPALA-7652:
---------------------------------------

[~dan@danburkert.com] I think we talked about this briefly once - is there a JIRA on the Kudu side for something like this?

> Fix BytesRead for Kudu scans
> ----------------------------
>
>                 Key: IMPALA-7652
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7652
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 3.1.0
>            Reporter: Thomas Tauber-Marshall
>            Priority: Major
>              Labels: newbie
>
> In the runtime profile, all scan nodes have a BytesRead counter. Kudu scan nodes do not actually set this counter, which creates confusion when Kudu scans report 0 bytes read even though they did in fact read data.
> We should either fill in this counter for Kudu scans, or if its difficult to get the count of bytes read from Kudu then we should eliminate the counter for Kudu scan node profiles.



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