poojanilangekar 44e69e8182 IMPALA-7749: Compute AggregationNode's memory estimate using input cardinality ...

Prior to this change, the AggregationNode's perInstanceCardinality
was influenced by the node's selectivity and limit. This was
incorrect because the hash table is constructed over the entire
input stream before any row batches are produced. This change
ensures that the input cardinality is used to determine the
perInstanceCardinality.

Testing:
Added a planner test which ensures that an AggregationNode with a
limit estimates memory based on the input cardinality.
Ran front-end and end-to-end tests affected by this change.

Change-Id: Ifd95d2ad5b677fca459c9c32b98f6176842161fc
Reviewed-on: http://gerrit.cloudera.org:8080/11806
Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>

2018-10-29 20:40:50 +00:00

..

queries/PlannerTest

IMPALA-7749: Compute AggregationNode's memory estimate using input cardinality

2018-10-29 20:40:50 +00:00

functional-planner_core.csv

Update benchmark tests to run against generic workload, data loading with scale factor, +more

2014-01-08 10:44:22 -08:00

functional-planner_dimensions.csv

Update benchmark tests to run against generic workload, data loading with scale factor, +more

2014-01-08 10:44:22 -08:00

functional-planner_exhaustive.csv

Update benchmark tests to run against generic workload, data loading with scale factor, +more

2014-01-08 10:44:22 -08:00

functional-planner_pairwise.csv

Update benchmark tests to run against generic workload, data loading with scale factor, +more

2014-01-08 10:44:22 -08:00