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

Posted to issues@kudu.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2016/06/03 21:29:59 UTC

[jira] [Resolved] (KUDU-1444) Get resource usage of a scan in KuduScanner

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

Jean-Daniel Cryans resolved KUDU-1444.
--------------------------------------
       Resolution: Fixed
         Assignee: ZhangZhen
    Fix Version/s: 1.0.0

Fixed in ece7b5653998db318e4baa5d57f27ba3a836731d.

> Get resource usage of a scan in KuduScanner
> -------------------------------------------
>
>                 Key: KUDU-1444
>                 URL: https://issues.apache.org/jira/browse/KUDU-1444
>             Project: Kudu
>          Issue Type: New Feature
>            Reporter: ZhangZhen
>            Assignee: ZhangZhen
>             Fix For: 1.0.0
>
>
> As Kudu supports predicates push down, bytes size of rows returned to the kudu client may differs a lot with the bytes size read from disk in tablet server side when running a scan. In some cases, the client side may need to know the actual resource usage. For example, impala may need this so it can estimate a query's actual resource usage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)