[
https://issues.apache.org/jira/browse/IMPALA-12383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765803#comment-17765803
]
ASF subversion and git services commented on IMPALA-12383:
----------------------------------------------------------
Commit 49a0445b5efe15992161144c33805055199c9969 in impala's branch
refs/heads/branch-4.3.0 from Michael Smith
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=49a0445b5 ]
IMPALA-12383: (Addendum) Use named params
Updates the call to add_test_dimensions to pass named parameters to
avoid any issues that might come up if additional parameters are added.
Change-Id: Ief492d054abbd00338e27ded9988141db750707c
Reviewed-on: http://gerrit.cloudera.org:8080/20483
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Michael Smith <[email protected]>
> Aggregation with num_nodes=1 and limit returns too many rows
> ------------------------------------------------------------
>
> Key: IMPALA-12383
> URL: https://issues.apache.org/jira/browse/IMPALA-12383
> Project: IMPALA
> Issue Type: Bug
> Components: Backend, Frontend
> Affects Versions: Impala 4.1.0
> Reporter: Michael Smith
> Assignee: Michael Smith
> Priority: Major
> Fix For: Impala 4.3.0
>
>
> With {{set num_nodes=1}} to select SingleNodePlanner, aggregations return too
> many rows:
> {code}
> > select distinct l_orderkey from tpch.lineitem limit 10;
> ...
> Fetched 16 row(s) in 0.12s
> > select ss_cdemo_sk from tpcds.store_sales group by ss_cdemo_sk limit 3;
> ...
> Fetched 7 row(s) in 0.14s
> {code}
> This looks like it's caused by changes in IMPALA-2581, which attempts to push
> down limits to pre-aggregation. In SingleNodePlanner, there is no
> pre-aggregation, which the patch appears to have failed to account for.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
