[
https://issues.apache.org/jira/browse/IMPALA-13188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891917#comment-17891917
]
ASF subversion and git services commented on IMPALA-13188:
----------------------------------------------------------
Commit 47b638e667dedd655f422609edff2ad14f7cd3f6 in impala's branch
refs/heads/master from Yida Wu
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=47b638e66 ]
IMPALA-13188: Add test that compute stats does not result in a different tuple
cache key
The patch introduces a new test, TestTupleCacheComputeStats, to
verify that compute stats does not change the tuple cache key.
The test creates a simple table with one row, runs an explain
on a basic query, then inserts more rows, computes the stats,
and reruns the same explain query. It compares the two results
to ensure that the cache keys are identical in the planning
phase.
Tests:
Passed the test.
Change-Id: I918232f0af3a6ab8c32823da4dba8f8cd31369d0
Reviewed-on: http://gerrit.cloudera.org:8080/21917
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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]
