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 2019/01/08 22:58:00 UTC

[jira] [Resolved] (BEAM-6110) Beam SQL join moves element timestamps to EOW sometimes, not always

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

Kenneth Knowles resolved BEAM-6110.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 2.10.0

> Beam SQL join moves element timestamps to EOW sometimes, not always
> -------------------------------------------------------------------
>
>                 Key: BEAM-6110
>                 URL: https://issues.apache.org/jira/browse/BEAM-6110
>             Project: Beam
>          Issue Type: Bug
>          Components: dsl-sql
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Major
>             Fix For: 2.10.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> When a CoGBK join is chosen, element timestamps move to EOW. When side input or lookup join is chosen, element timestamps are the timestamps from the main input element. In SQL sementics, these timestamps are not observable, as windowing is assigned at the next GROUP BY. So we just need the output to hold the watermark so that nothing becomes late or droppable, which implies we need to use MIN timestamp combiner.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)