You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
single_distinct_to_groupby not applied to DataFrame API count(DISTINCT) #23401
The SingleDistinctToGroupBy optimizer rule rewrites a grouped count(DISTINCT col) into a cheaper nested double aggregate. It fires for plans built by the SQL planner but not for the logically-equivalent plan built by the DataFrame API, so the DataFrame path runs materially slower for the same query.
The divergence is caused by how each front-end places the output alias:
SQL (count(DISTINCT v) AS n): the alias becomes an outer Projection; Aggregate.aggr_expr holds a bare Expr::AggregateFunction.
DataFrame API (count(col("v")).distinct().alias("n")): the alias wraps the aggregate directly, so aggr_expr holds Expr::Alias(AggregateFunction).
is_single_distinct_agg only matches a bare Expr::AggregateFunction and returns false for the aliased shape, so the rule never fires for the DataFrame API.
Activity
fix: apply single_distinct_to_groupby to aliased DataFrame API aggreg…
fix: apply single_distinct_to_groupby to aliased DataFrame API aggreg…
fix: apply single_distinct_to_groupby to aliased DataFrame API aggreg…
fix: apply single_distinct_to_groupby to aliased DataFrame API aggreg…
fix: apply single_distinct_to_groupby to aliased DataFrame API aggreg…
qazxcdswe123 commentedon Jul 9, 2026
I think this might be relavant #1468? (But not helpful though)
fangchenli commentedon Jul 9, 2026
Yes, related. But #1468 has a bigger scope.