You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Alessandro Solimando (Jira)" <ji...@apache.org> on 2026/04/22 05:44:00 UTC
[jira] [Commented] (CALCITE-7485) FIRST_VALUE/LAST_VALUE should only be defined for window aggregates
[ https://issues.apache.org/jira/browse/CALCITE-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18075345#comment-18075345 ]
Alessandro Solimando commented on CALCITE-7485:
-----------------------------------------------
Makes sense, but to be sure maybe you can look this up in the SQL standard or verify with Postgres or similar that this is actually the case?
> FIRST_VALUE/LAST_VALUE should only be defined for window aggregates
> -------------------------------------------------------------------
>
> Key: CALCITE-7485
> URL: https://issues.apache.org/jira/browse/CALCITE-7485
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.41.0
> Reporter: Yu Xu
> Priority: Major
>
> FIRST_VALUE and LAST_VALUE are only defined for window aggregates, but can be used without window clause in current main branch.
> test case would be passed as follow:
>
> {code:java}
> @Test void testFirstAndLastAggFunctionsOfGroupByKeys() {
> final String sql = "select sal, first_value(sal) as sal_first, last_value(sal) as sal_last from emp group by sal, deptno\n";
> sql(sql).check();
> } {code}
> maybe we should fix the issue.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)