[
https://issues.apache.org/jira/browse/BEAM-6110?focusedWorklogId=451954&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-451954
]
ASF GitHub Bot logged work on BEAM-6110:
----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jun/20 01:58
Start Date: 28/Jun/20 01:58
Worklog Time Spent: 10m
Work Description: amaliujia commented on pull request #12112:
URL: https://github.com/apache/beam/pull/12112#issuecomment-650669884
Ah the `StreamingSQLTest.testZetaSQLNestedQueryFour` failed because nothing
was emitted from that test pipeline, which doesn't look right.
----------------------------------------------------------------
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: 451954)
Time Spent: 1h 50m (was: 1h 40m)
> 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: P2
> Fix For: 2.10.0
>
> Time Spent: 1h 50m
> 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
(v8.3.4#803005)
