You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tajo.apache.org by "Sergio Esteves (JIRA)" <ji...@apache.org> on 2013/10/04 04:12:42 UTC

[jira] [Updated] (TAJO-35) Hybrid Hash Join Operator

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

Sergio Esteves updated TAJO-35:
-------------------------------

    Status: Patch Available  (was: In Progress)

> Hybrid Hash Join Operator
> -------------------------
>
>                 Key: TAJO-35
>                 URL: https://issues.apache.org/jira/browse/TAJO-35
>             Project: Tajo
>          Issue Type: New Feature
>          Components: physical operator
>            Reporter: Hyunsik Choi
>            Assignee: Sergio Esteves
>              Labels: gsoc, gsoc2013, mentor
>         Attachments: TAJO-35.patch
>
>
> The hybrid hash join algorithm is well known as the best join algorithm which takes advantage of more available memory. The goal of this proposal is to implement HybridHashJoinExec class subclassed from PhysicalExec. Its original literature is "Join processing in database systems with large main memories" (http://www.cs.ucr.edu/~tsotras/cs236/W13/join.pdf). In addition, you could find many other materials available in the web.



--
This message was sent by Atlassian JIRA
(v6.1#6144)