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

Victoria Markman commented on DRILL-658:
----------------------------------------

It's not just multiple distinct counts without grouping, also cases where you 
mix distinct and non distinct aggregates, like query below:

{code}
0: jdbc:drill:schema=dfs> select avg(o_totalprice) + avg(distinct o_totalprice) 
from cp.`tpch/orders.parquet`;
Query failed: Query failed: Unexpected exception during fragment 
initialization: Node [rel#6320:Subset#3.LOGICAL.ANY([]).[]] could not be 
implemented; planner state:
{code}

> Add support for multiple distinct counts without a grouping key.
> ----------------------------------------------------------------
>
>                 Key: DRILL-658
>                 URL: https://issues.apache.org/jira/browse/DRILL-658
>             Project: Apache Drill
>          Issue Type: New Feature
>          Components: Query Planning & Optimization
>            Reporter: Chun Chang
>            Assignee: Jinfeng Ni
>             Fix For: Future
>
>
> postgres:
> foodmart=# select count(distinct(c_int)), count(distinct(c_bigint)), 
> count(distinct(c_float4)), count(distinct(c_float8)) from data;
>  count | count | count | count
> -------+-------+-------+-------
>     21 |    23 |    22 |    20
> (1 row)
> drill:
> 0: jdbc:drill:schema=dfs> select count(distinct(c_int)), 
> count(distinct(c_bigint)), count(distinct(c_float4)), 
> count(distinct(c_float8)) from data;
> Query failed: org.apache.drill.exec.rpc.RpcException: Remote failure while 
> running query.[error_id: "658d1c88-3968-457f-82e1-26c76ff7b54b"
> endpoint {
>   address: "qa-node120.qa.lab"
>   user_port: 31010
>   control_port: 31011
>   data_port: 31012
> }
> error_type: 0
> message: "Failure while parsing sql. < CannotPlanException:[ Node 
> [rel#5852:Subset#33.PHYSICAL.SINGLETON([]).[]] could not be implemented;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to