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

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 18:13:00 UTC

[jira] [Updated] (BEAM-12011) WindowFn.getOutputTime break joins, adds needless complexity

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

Kenneth Knowles updated BEAM-12011:
-----------------------------------
    Fix Version/s: 2.30.0
       Resolution: Fixed
           Status: Resolved  (was: In Progress)

> WindowFn.getOutputTime break joins, adds needless complexity
> ------------------------------------------------------------
>
>                 Key: BEAM-12011
>                 URL: https://issues.apache.org/jira/browse/BEAM-12011
>             Project: Beam
>          Issue Type: Bug
>          Components: beam-model
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: P2
>             Fix For: 2.30.0
>
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
>
> See https://lists.apache.org/thread.html/r99d0efa70f83815e17a1dbfb94effd16b38176046ac8ffbfe371c895%40%3Cdev.beam.apache.org%3E
> The consensus is that we really shouldn't be producing weird output, even if it causes a watermark problem we should solve it another way. It breaks CoGBK joins, and new runner authors have even missed the existence of the need to call into a UDF (hence implementing SlidingWindows the natural way instead of this strange way)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)