[
https://issues.apache.org/jira/browse/CALCITE-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhen Chen resolved CALCITE-7242.
--------------------------------
Fix Version/s: 1.43.0
Assignee: Zhen Chen
Resolution: Fixed
Fixed in
[{{2bdc6af}}|https://github.com/apache/calcite/commit/2bdc6af448693c81da3e16208b1af2325fee1d2a]
{{Thanks for report the feature [~zwhtx] }}
{{Thanks for review [~mbudiu]}}
> Implement a rule to eliminate LITERAL_AGG so that other databases can handle
> it
> -------------------------------------------------------------------------------
>
> Key: CALCITE-7242
> URL: https://issues.apache.org/jira/browse/CALCITE-7242
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: weihua zhang
> Assignee: Zhen Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.43.0
>
>
> Calcite can create an Aggregate RelNode with LITERAL_AGG AggregateCall to
> check for existence in a subquery. In this case, the Aggregate will do a
> group by, and just spit out a literal value for each row.
> The LITERAL_AGG function does not exist in other databases. In order to
> create a RelNode structure that other databases supports, this Aggregate is
> turned into an Aggregate that still does the "group by" on the relevant
> groups, but places a Project RelNode on top that returns the literal value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
