[
https://issues.apache.org/jira/browse/IGNITE-23813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-23813:
--------------------------------------
Description:
Current Implementation of LITERAL_AGG aggregate function (see LiteralVal) is
not correct because it always produces a result of type BOOLEAN. But according
to CALCITE-4334 this function can return a value if an arbitrary type.
The implementation of LITERAL_AGG aggregate function should conform to its
definition described in CALCITE-4334:
- it should support all natively supported literals.
- It should use pre-operands provided by AggregateCall (rexList).
was:
Current Implementation of LITERAL_AGG aggregate function (see LiteralVal) is
not correct because it always produces a result of type BOOLEAN. But according
to https://issues.apache.org/jira/browse/CALCITE-4334 this function can return
a value if an arbitrary type.
The implementation of LITERAL_AGG aggregate function should conform to its
definition described in CALCITE-4334:
- it should support all natively supported literals.
- It should use pre-operands provided by AggregateCall (rexList).
> Sql. Provide correct implementation of LITERAL_AGG aggregate function
> ---------------------------------------------------------------------
>
> Key: IGNITE-23813
> URL: https://issues.apache.org/jira/browse/IGNITE-23813
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Maksim Zhuravkov
> Priority: Major
>
> Current Implementation of LITERAL_AGG aggregate function (see LiteralVal) is
> not correct because it always produces a result of type BOOLEAN. But
> according to CALCITE-4334 this function can return a value if an arbitrary
> type.
> The implementation of LITERAL_AGG aggregate function should conform to its
> definition described in CALCITE-4334:
> - it should support all natively supported literals.
> - It should use pre-operands provided by AggregateCall (rexList).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
