flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt Young (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-11871) Introduce LongHashTable to improve performance when join key fits in long
Date Tue, 19 Mar 2019 15:18:00 GMT

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

Kurt Young closed FLINK-11871.
------------------------------
       Resolution: Implemented
    Fix Version/s: 1.9.0

fixed inĀ 299747fc698d99ff826a810b2b354db53b34848c

> Introduce LongHashTable to improve performance when join key fits in long
> -------------------------------------------------------------------------
>
>                 Key: FLINK-11871
>                 URL: https://issues.apache.org/jira/browse/FLINK-11871
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Operators
>            Reporter: Kurt Young
>            Assignee: Kurt Young
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We can do further optimizations if we know the join key fits in long, a single long field
or two integer fields are both ok. For example, we can combine the hash code and actual key
into one field, there will be no hash collision, can save a lot of unnecessary logic.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message