You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2022/10/26 15:48:00 UTC
[jira] [Updated] (IGNITE-13744) Calcite. Use TableSpool for IgniteNestedLoopJoin
[ https://issues.apache.org/jira/browse/IGNITE-13744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-13744:
---------------------------------------
Labels: calcite calcite2-required calcite3-required iep-96 (was: calcite calcite2-required calcite3-required)
> Calcite. Use TableSpool for IgniteNestedLoopJoin
> ------------------------------------------------
>
> Key: IGNITE-13744
> URL: https://issues.apache.org/jira/browse/IGNITE-13744
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Taras Ledkov
> Assignee: Evgeny Stanilovsky
> Priority: Minor
> Labels: calcite, calcite2-required, calcite3-required, iep-96
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Now {{NestedLoopJoinNode}} uses internal buffer to save all rows of the right input.
> We have to do refactoring {{IgniteNestedLoopJoin}} to use rewind of the right input and use TableSpool for not rewindable inputs.
> This refactoring separates implementation the join logic from materialization of the right input if it is needed. In the future we can use disk offload for TableSpool etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)