You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Ruben Quesada Lopez (Jira)" <ji...@apache.org> on 2019/08/23 07:17:00 UTC

[jira] [Resolved] (CALCITE-2979) Add a batch-based nested loop join algorithm

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

Ruben Quesada Lopez resolved CALCITE-2979.
------------------------------------------
    Resolution: Fixed

Fixed via https://github.com/apache/calcite/commit/a8f9e4ee02c4253e1cbc150cbe3af8791a7beda8

Thanks for the PR [~khawlamhb]!

> Add a batch-based nested loop join algorithm
> --------------------------------------------
>
>                 Key: CALCITE-2979
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2979
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.19.0
>            Reporter: Stamatis Zampetakis
>            Assignee: Khawla Mouhoubi
>            Priority: Major
>              Labels: performance, pull-request-available
>             Fix For: 1.21.0
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Currently, Calcite provides a tuple-based nested loop join algorithm implemented through EnumerableCorrelate and EnumerableDefaults.correlateJoin. This means that for each tuple of the outer relation we probe (set variables) in the inner relation.
> The goal of this issue is to add new algorithm (or extend the correlateJoin method) which first gathers blocks (batches) of tuples from the outer relation and then probes the inner relation once per block.
> There are cases (eg., indexes) where the inner relation can be accessed by more than one value which can greatly improve the performance in particular when the outer relation is big.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)