[
https://issues.apache.org/jira/browse/BEAM-13736?focusedWorklogId=714978&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-714978
]
ASF GitHub Bot logged work on BEAM-13736:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jan/22 17:03
Start Date: 25/Jan/22 17:03
Worklog Time Spent: 10m
Work Description: codecov[bot] edited a comment on pull request #16603:
URL: https://github.com/apache/beam/pull/16603#issuecomment-1020828161
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 714978)
Time Spent: 1.5h (was: 1h 20m)
> [Go SDK] Fix hash collision risk in Combiner Lifting cache
> ----------------------------------------------------------
>
> Key: BEAM-13736
> URL: https://issues.apache.org/jira/browse/BEAM-13736
> Project: Beam
> Issue Type: Improvement
> Components: sdk-go
> Reporter: Robert Burke
> Assignee: Robert Burke
> Priority: P2
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Relying only on a hash is brittle for map implementations, and can lead to
> correctness issues when keys collide.
> While the Go SDK implementation is leaning on the Go map, we need to rely on
> byte equality so we need to fend for ourselves a bit, and handle overflow
> buckets and the like.
> We won't go so far as to do a rehash or similar balancing techniques as it's
> not clear that between the caches' size constraint, and the evenness of the
> hash function that they are all that likely.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
