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

Yida Wu resolved IMPALA-13188.
------------------------------
    Fix Version/s: Impala 4.5.0
       Resolution: Fixed

> Add test that compute stats does not result in a different tuple cache key
> --------------------------------------------------------------------------
>
>                 Key: IMPALA-13188
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13188
>             Project: IMPALA
>          Issue Type: Task
>          Components: Frontend
>    Affects Versions: Impala 4.5.0
>            Reporter: Joe McDonnell
>            Assignee: Yida Wu
>            Priority: Major
>             Fix For: Impala 4.5.0
>
>
> If someone runs "compute stats" on the underlying tables for a query, the 
> tuple cache key should only change if the plan actually changes. The resource 
> estimates should not be incorporated into the tuple cache key as they have no 
> semantic impact. The code already excludes the resource estimates from the 
> key for the PlanNode, but we should have tests for computing stats and 
> verifying that the key doesn't change.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to