You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "pengfei.zhan (Jira)" <ji...@apache.org> on 2024/04/10 02:38:00 UTC

[jira] [Assigned] (KYLIN-5817) After sending the query, the number of scanRows and scanBytes in response are inaccurate

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

pengfei.zhan reassigned KYLIN-5817:
-----------------------------------

    Assignee: zhimin wu

> After sending the query, the number of scanRows and scanBytes in response are inaccurate
> ----------------------------------------------------------------------------------------
>
>                 Key: KYLIN-5817
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5817
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Query Engine
>    Affects Versions: 5.0-beta
>            Reporter: zhimin wu
>            Assignee: zhimin wu
>            Priority: Major
>             Fix For: 5.0.0
>
>
> h3. Background
> When KE calls the query interface, it is found that the scan row count {{scanRows}} and scan byte count {{scanBytes}} in the response are not accurate.
> h3. Root Cause
> The query interface internally calls the {{collectAdaptiveSparkPlanExecMetrics}} method of {{{}QueryMetricUtils{}}}. When iterating through {{{}exec.children.foreach{}}}, if the {{child}} is a {{{}SparkPlan{}}}, each time the results of the new {{child}} overwrite the {{newScanRow}} and {{newScanBytes}} variables without adding them up.
> h3. Dev Design
> To address the issue, replace the assignment operator {{=}} with the compound addition assignment operator {{+=}} to ensure that the results are properly accumulated. This change will allow for the correct aggregation of scan row count and scan byte count in each iteration.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)