[
https://issues.apache.org/jira/browse/BEAM-5250?focusedWorklogId=140514&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-140514
]
ASF GitHub Bot logged work on BEAM-5250:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Sep/18 09:24
Start Date: 03/Sep/18 09:24
Worklog Time Spent: 10m
Work Description: mxm commented on issue #6315: [BEAM-5250] Fix
GlobalWindow's max timestamp in Python SDK
URL: https://github.com/apache/beam/pull/6315#issuecomment-418055824
>This is very surprising behavior to me and I don't see a good reason for
this being the case. Why is this the case in the Java SDK?
If you look at `GlobalWindow`, it explains that triggers use
`maxTimestamp()` to set the timer. A trigger is triggered when the Watermark
passes the trigger time. So this was initially introduced to be able to trigger
global windows, which used MAX_TIMESTAMP previously.
> Shouldn't we make the formal spec do the more obvious thing rather than
carry over what seems like a longstanding hack from one SDK to the formal spec?
Would be desirable to fix this, e.g. have a special rule for triggers to
always fire at MAX_TIMESTAMP.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 140514)
Time Spent: 50m (was: 40m)
> Python Wordcount fails with Flink portable streaming
> ----------------------------------------------------
>
> Key: BEAM-5250
> URL: https://issues.apache.org/jira/browse/BEAM-5250
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: Thomas Weise
> Assignee: Maximilian Michels
> Priority: Major
> Labels: portability
> Time Spent: 50m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
