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

Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2022/08/03 09:41:00 UTC

[jira] [Updated] (IGNITE-17437) SQL. Investigate of support LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate function for ignite 3

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

Yury Gerzhedovich updated IGNITE-17437:
---------------------------------------
    Summary: SQL. Investigate of support LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate function for ignite 3  (was: SQL. Support LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate function for ignite 3)

> SQL. Investigate of support LISTAGG (aka GROUP_CONCAT, STRING_AGG) aggregate function for ignite 3
> --------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-17437
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17437
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Yury Gerzhedovich
>            Priority: Major
>              Labels: ignite-3
>
> LISTAGG function implemented for Ignite 2, however for Ignite 3 need to rethink design of the solution.  
> TBD: reasons why we want to do it differently.
> Let's investigate possible ways to implement it.
> As a result need to implement it, create ticket to document it and unmute the test_order_variable_size_payload.test_ignore test



--
This message was sent by Atlassian Jira
(v8.20.10#820010)