You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2024/04/16 07:35:00 UTC

[jira] [Assigned] (IGNITE-21720) Sql. Implement hash join

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

Evgeny Stanilovsky reassigned IGNITE-21720:
-------------------------------------------

    Assignee: Evgeny Stanilovsky

> Sql. Implement hash join
> ------------------------
>
>                 Key: IGNITE-21720
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21720
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Assignee: Evgeny Stanilovsky
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> At the moment, we have two basic join strategies: nested loop and merge. Looks like we can significantly improve performance of equi-joins by introducing one more strategy: hash join.
> h3. Implementation Notes
> Looks like we can unify {{NestedLoopJoinNode}} in order to support both NL and HASH strategies. For this, we need to introduce abstraction for {{rightMaterialize}} part that will have two methods: {{void push(RowT r)}} and {{List<RowT> lookup(RowT r)}}. Push should be used during filling stage; lookup should be used within join main loop.



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