[
https://issues.apache.org/jira/browse/KYLIN-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504754#comment-17504754
]
ASF GitHub Bot commented on KYLIN-5168:
---------------------------------------
sleep1661 commented on pull request #1831:
URL: https://github.com/apache/kylin/pull/1831#issuecomment-1064835983
@hit-lacus @zhangayqian could you help take a look when you have time?
Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Add bytesRead metric to KylinFileSourceScanExec
> -----------------------------------------------
>
> Key: KYLIN-5168
> URL: https://issues.apache.org/jira/browse/KYLIN-5168
> Project: Kylin
> Issue Type: Improvement
> Components: Query Engine
> Affects Versions: v4.0.1
> Reporter: hujiahua
> Priority: Major
>
> Currently Kylin FileSourceScanExec has no relevant metirc about how many
> bytes of data are actually read, as a result, the actual output of scanByte
> metric of kylin query is the total source file size scanned, rather than the
> actual read data size. So I think a metric like this should be added to
> KylinFileSourceScanExec.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
