You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Arina Ielchiieva (Jira)" <ji...@apache.org> on 2019/11/04 12:45:00 UTC
[jira] [Updated] (DRILL-4667) Improve memory footprint of broadcast
joins
[ https://issues.apache.org/jira/browse/DRILL-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arina Ielchiieva updated DRILL-4667:
------------------------------------
Fix Version/s: (was: 1.17.0)
> Improve memory footprint of broadcast joins
> -------------------------------------------
>
> Key: DRILL-4667
> URL: https://issues.apache.org/jira/browse/DRILL-4667
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Relational Operators
> Affects Versions: 1.6.0
> Reporter: Aman Sinha
> Assignee: Boaz Ben-Zvi
> Priority: Major
>
> For broadcast joins, currently Drill optimizes the data transfer across the network for broadcast table by sending a single copy to the receiving node which then distributes it to all minor fragments running on that particular node. However, each minor fragment builds its own hash table (for a hash join) using this broadcast table. We can substantially improve the memory footprint by having a shared copy of the hash table among multiple minor fragments on a node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)