You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/04/10 01:40:00 UTC

[jira] [Updated] (CALCITE-6945) Use LITERAL_AGG to simplify SubQueryRemoveRule by avoiding the extra Project

     [ https://issues.apache.org/jira/browse/CALCITE-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated CALCITE-6945:
------------------------------------
    Labels: pull-request-available  (was: )

> 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)