You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Daniel Oliveira (Jira)" <ji...@apache.org> on 2020/03/17 00:42:00 UTC

[jira] [Updated] (BEAM-9526) Bug in top.LargestPerKey, disappearing elements.

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

Daniel Oliveira updated BEAM-9526:
----------------------------------
    Status: Open  (was: Triage Needed)

> 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
>
> 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)