[
https://issues.apache.org/jira/browse/TAJO-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162986#comment-14162986
]
Hudson commented on TAJO-1010:
------------------------------
SUCCESS: Integrated in Tajo-master-CODEGEN-build #38 (See
[https://builds.apache.org/job/Tajo-master-CODEGEN-build/38/])
TAJO-1010: Improve multiple DISTINCT aggregation. (Hyoungjun Kim and jaehwa)
(blrunner: rev 0dfa3972c6a52d785b8e55f91d0906456a3926b3)
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/physical/DistinctGroupbyFirstAggregationExec.java
* tajo-common/src/main/java/org/apache/tajo/SessionVars.java
*
tajo-core/src/test/resources/queries/TestGroupByQuery/testDistinctAggregation8.sql
* tajo-storage/src/main/java/org/apache/tajo/storage/TupleComparator.java
* tajo-core/src/main/java/org/apache/tajo/master/querymaster/Repartitioner.java
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/logical/DistinctGroupbyNode.java
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/physical/DistinctGroupbyThirdAggregationExec.java
*
tajo-core/src/test/resources/results/TestGroupByQuery/testDistinctAggregation8.result
*
tajo-core/src/test/resources/results/TestGroupByQuery/testDistinctAggregation_case10.result
* tajo-core/src/main/java/org/apache/tajo/engine/planner/enforce/Enforcer.java
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/global/GlobalPlanner.java
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/global/builder/DistinctGroupbyBuilder.java
*
tajo-core/src/test/resources/results/TestGroupByQuery/testDistinctAggregation_case9.result
*
tajo-core/src/test/resources/queries/TestGroupByQuery/testDistinctAggregation_case9.sql
*
tajo-core/src/test/resources/queries/TestGroupByQuery/testDistinctAggregation_case10.sql
* tajo-core/src/main/proto/TajoWorkerProtocol.proto
*
tajo-core/src/main/java/org/apache/tajo/engine/eval/AggregationFunctionCallEval.java
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/physical/DistinctGroupbySecondAggregationExec.java
*
tajo-core/src/main/java/org/apache/tajo/engine/planner/PhysicalPlannerImpl.java
* tajo-core/src/test/resources/results/TestTajoCli/testHelpSessionVars.result
* tajo-core/src/main/java/org/apache/tajo/master/querymaster/SubQuery.java
* CHANGES
* tajo-core/src/test/java/org/apache/tajo/engine/query/TestGroupByQuery.java
* tajo-common/src/main/java/org/apache/tajo/conf/TajoConf.java
> Improve multiple DISTINCT aggregation.
> --------------------------------------
>
> Key: TAJO-1010
> URL: https://issues.apache.org/jira/browse/TAJO-1010
> Project: Tajo
> Issue Type: Improvement
> Components: planner/optimizer
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
> Fix For: 0.9.0
>
>
> Currently, tajo provides three stage for optimizing distinct query
> aggregation. But it just supports one column for distinct aggregation as
> follows:
> {code:title=Query1|borderStyle=solid}
> select a.flag, count(distinct a.id) as cnt, sum(distinct a.id) as total
> from table1
> group by a.flag
> {code}
> If you write two more columns for distinct aggregation, you can't apply
> optimized distinct aggregation as follows:
> {code:title=Query2|borderStyle=solid}
> select a.flag, count(distinct a.id) as cnt, sum(distinct a.id) as total
> , count(distinct a.name) as cnt2, count(distinct a.code) as cnt3
> from table1
> group by a.flag
> {code}
> In this case, you may see low performance for your query. Thus, we need to
> improve multiple DISTINCT aggregation. Correctly, we should support three
> stage for multiple DISTINCT aggregation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
