You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2023/08/23 13:08:00 UTC

[jira] [Updated] (IGNITE-19992) Sql. Rework execution of 2-phase set operators

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

Konstantin Orlov updated IGNITE-19992:
--------------------------------------
    Fix Version/s: 3.0.0-beta2

> Sql. Rework execution of 2-phase set operators
> ----------------------------------------------
>
>                 Key: IGNITE-19992
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19992
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Assignee: Maksim Zhuravkov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 7h
>  Remaining Estimate: 0h
>
> As of now, both {{IntersectNode}} and {{MinusNode}} use complex structures as result of MAP phase (see {{org.apache.ignite.internal.sql.engine.exec.rel.AbstractSetOpNode.Grouping#getOnMapper}}; it emits rows cardinality of 2, where first column is entire group key, and second column is an array of counters). This prevents us from migrating sql runtime to BinaryTuple-based rows, because currently BinaryTuple does not support nested structures.
> Let's rework those node to inline group key and counters into plain row.



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