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

Riza Suminto resolved IMPALA-13119.
-----------------------------------
    Fix Version/s: Impala 4.5.0
       Resolution: Fixed

> CostingSegment.java is initialized with wrong cost
> --------------------------------------------------
>
>                 Key: IMPALA-13119
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13119
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 4.4.0
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Major
>             Fix For: Impala 4.5.0
>
>
> CostingSegment.java has two public constructor: one accept PlanNode, while 
> the other accept DataSink as parameter. Both call appendCost method, which 
> sum the additionalCost with the segment's current cost_.
> However, if cost_ were ProcessingCost.zero(), it can mistakenly 
> setNumRowToConsume to 0.
> [https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/planner/CostingSegment.java#L114]
>  
> The public constructor should just initialize cost_ with ProcessingCost from 
> PlanNode or DataSink from constructor.



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

Reply via email to