[
https://issues.apache.org/jira/browse/FLINK-11856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt Young closed FLINK-11856.
------------------------------
Resolution: Implemented
Fix Version/s: 1.9.0
fixed in 5968206f843a58e10e3db58cde3407bb3608d085
> Introduce BinaryHashTable to batch table runtime
> ------------------------------------------------
>
> Key: FLINK-11856
> URL: https://issues.apache.org/jira/browse/FLINK-11856
> 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: 20m
> Remaining Estimate: 0h
>
> Once we have BinaryRow, we should also introduce the hash table which stored
> all rows in binary format. It has multiple benefits if we knows the binary
> format about the build side row and probe side row. For example, we can
> directly compare on byte arrays when we want to check if build key and probe
> key equals. We can also eliminate lots of deserialize cost when we want to
> get a row instance from some binary data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
