[ 
https://issues.apache.org/jira/browse/IMPALA-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685908#comment-16685908
 ] 

ASF subversion and git services commented on IMPALA-7761:
---------------------------------------------------------

Commit cd26e807f18ef5fa729d7e15d0492a1284990122 in impala's branch 
refs/heads/master from [~twmarshall]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=cd26e80 ]

IMPALA-7761: Add multiple DISTINCT to targeted perf and stress test

IMPALA-110 added support for queries with multiple DISTINCT aggregates
in a single select list. This patch adds queries to test this
functionality to our targeted-perf workloads and fixes some incorrect
return types in another targeted-perf aggregation query.

It also adds some targeted queries to the stress test by extending the
regex for stress test files to accept files of the form
'tpch-stress-*' and to allow for multiple tests per file.

Testing:
- Added an e2e test that runs the stress test file.

Change-Id: I400aaf6b6620b4001895eafff785956bffb312c9
Reviewed-on: http://gerrit.cloudera.org:8080/11805
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Add multiple count distinct to targeted stress and targeted perf
> ----------------------------------------------------------------
>
>                 Key: IMPALA-7761
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7761
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: Impala 3.1.0
>            Reporter: Thomas Tauber-Marshall
>            Assignee: Thomas Tauber-Marshall
>            Priority: Blocker
>
> With IMPALA-110 in, we should add queries with multiple count distinct to 
> targeted stress and targeted perf



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to