[
https://issues.apache.org/jira/browse/CALCITE-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17943993#comment-17943993
]
xiong duan commented on CALCITE-6945:
-------------------------------------
Fixed in
[9b91d31|https://github.com/apache/calcite/commit/9b91d319e720ce03cf4d8befae0d5a192a93be99].
Thanks for the review [~mbudiu] .
> Use LITERAL_AGG to simplify SubQueryRemoveRule by avoiding the extra Project
> -----------------------------------------------------------------------------
>
> Key: CALCITE-6945
> URL: https://issues.apache.org/jira/browse/CALCITE-6945
> Project: Calcite
> Issue Type: Bug
> Reporter: xiong duan
> Assignee: xiong duan
> Priority: Major
> Labels: pull-request-available
>
> For example, when rewriting sub-queries (see {{{}SubQueryRemoveRule{}}}) we
> introduce add "true as indicator" to the SELECT clause of sub-queries. It can
> be used to detect rows generated by an outer join. If it is an aggregate
> query, we would have to write "min(true) as indicator", which necessitates an
> extra {{Project}} below the {{Aggregate}} to provide the "true" value. The
> LITERAL_AGG aggregate function allows us to avoid the extra {{{}Project{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
