[
https://issues.apache.org/jira/browse/DRILL-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247040#comment-16247040
]
ASF GitHub Bot commented on DRILL-5691:
---------------------------------------
Github user weijietong commented on the issue:
https://github.com/apache/drill/pull/889
@amansinha100 thanks for sharing the information. Got your point. I think
your propose on
[CALCITE-1048](https://issues.apache.org/jira/browse/CALCITE-1048) is possible.
Since [CALCITE-794](https://issues.apache.org/jira/browse/CALCITE-794) has
completed at version 1.6 ,it seems there's a more perfect solution( to get the
least max number of all the rels of the RelSubSet). But due to Drill's Caclite
version is still based on 1.4 , I support your current temp solution. Only
wonder that whether the explicitly searched RelNode's (such as
DrillAggregateRel) maxRowCount can represent the best RelNode's maxRowCount ?
> multiple count distinct query planning error at physical phase
> ---------------------------------------------------------------
>
> Key: DRILL-5691
> URL: https://issues.apache.org/jira/browse/DRILL-5691
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Relational Operators
> Affects Versions: 1.9.0, 1.10.0
> Reporter: weijie.tong
>
> I materialized the count distinct query result in a cache , added a plugin
> rule to translate the (Aggregate、Aggregate、Project、Scan) or
> (Aggregate、Aggregate、Scan) to (Project、Scan) at the PARTITION_PRUNING phase.
> Then ,once user issue count distinct queries , it will be translated to query
> the cache to get the result.
> eg1: " select count(*),sum(a) ,count(distinct b) from t where dt=xx "
> eg2:"select count(*),sum(a) ,count(distinct b) ,count(distinct c) from t
> where dt=xxx "
> eg3:"select count(distinct b), count(distinct c) from t where dt=xxx"
> eg1 will be right and have a query result as I expected , but eg2 will be
> wrong at the physical phase.The error info is here:
> https://gist.github.com/weijietong/1b8ed12db9490bf006e8b3fe0ee52269.
> eg3 will also get the similar error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
