[
https://issues.apache.org/jira/browse/CALCITE-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987051#comment-16987051
]
Ruben Q L commented on CALCITE-3546:
------------------------------------
While working on CALCITE-3535, we found out that the "traditional"
implementation of nested loop join does not close all its resources.
I will fix the issue in the current ticket.
> Improve EnumerableDefaults nested loop join
> -------------------------------------------
>
> Key: CALCITE-3546
> URL: https://issues.apache.org/jira/browse/CALCITE-3546
> Project: Calcite
> Issue Type: Improvement
> Affects Versions: 1.21.0
> Reporter: Ruben Q L
> Assignee: Ruben Q L
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.22.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> The current implementation of {{EnumerableDefaults#nestedLoopJoin}} builds
> the complete join result in a list before returning it. As specified in a
> comment there, this is "easy, but hogs memory". Also, it is not very
> efficient if after the join there is a LIMIT.
> An alternative implementation of nested loop join can be proposed, based on
> iterating through the outer an inner enumerables, and returning the results
> step by step (something similar to {{EnumerableDefaults#correlateJoin}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
