[
https://issues.apache.org/jira/browse/BEAM-9526?focusedWorklogId=405554&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-405554
]
ASF GitHub Bot logged work on BEAM-9526:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Mar/20 16:21
Start Date: 18/Mar/20 16:21
Worklog Time Spent: 10m
Work Description: lostluck commented on issue #11143: [BEAM-9526] Add
missing unmarshalling in top.LargestPerKey.
URL: https://github.com/apache/beam/pull/11143#issuecomment-600727682
Thanks! LGTM
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 405554)
Time Spent: 0.5h (was: 20m)
> Bug in top.LargestPerKey, disappearing elements.
> ------------------------------------------------
>
> Key: BEAM-9526
> URL: https://issues.apache.org/jira/browse/BEAM-9526
> Project: Beam
> Issue Type: Bug
> Components: sdk-go
> Reporter: Daniel Oliveira
> Assignee: Daniel Oliveira
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There's a bug in top.LargestPerKey that appears when running it on a runner
> that has combiner lifting. Since it's similar to a GBK, we should be
> inputting a K, V and receiving a K, []V as output. When the runner has
> combiner lifting, the []V always contains an empty slice.
>
> I already found the fix for this, just logging this to attach it to the PR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
