[ https://issues.apache.org/jira/browse/BEAM-9573?focusedWorklogId=410603&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-410603 ]
ASF GitHub Bot logged work on BEAM-9573: ---------------------------------------- Author: ASF GitHub Bot Created on: 26/Mar/20 20:52 Start Date: 26/Mar/20 20:52 Worklog Time Spent: 10m Work Description: mxm commented on issue #11220: [BEAM-9573][release-2.20] Correct computing of watermark hold for timer output timestamp URL: https://github.com/apache/beam/pull/11220#issuecomment-604679224 Error prone errors in the build: ``` 20:42:09 * What went wrong: 20:42:09 Execution failed for task ':model:pipeline:compileJava'. 20:42:09 > Could not resolve all files for configuration ':model:pipeline:errorprone'. 20:42:09 > Could not resolve com.google.errorprone:error_prone_core:latest.release. 20:42:09 Required by: 20:42:09 project :model:pipeline 20:42:09 > Could not resolve com.google.errorprone:error_prone_core:2.3.4-SNAPSHOT. 20:42:09 > Unable to load Maven meta-data from https://oss.sonatype.org/content/repositories/staging/com/google/errorprone/error_prone_core/2.3.4-SNAPSHOT/maven-metadata.xml. 20:42:09 > Could not HEAD 'https://oss.sonatype.org/content/repositories/staging/com/google/errorprone/error_prone_core/2.3.4-SNAPSHOT/maven-metadata.xml'. Received status code 502 from server: Bad Gateway 20:42:09 ``` ---------------------------------------------------------------- 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: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 410603) Time Spent: 7h 10m (was: 7h) > Watermark hold for timer output timestamp is not computed correctly > ------------------------------------------------------------------- > > Key: BEAM-9573 > URL: https://issues.apache.org/jira/browse/BEAM-9573 > Project: Beam > Issue Type: Bug > Components: runner-flink > Affects Versions: 2.20.0 > Reporter: Maximilian Michels > Assignee: Maximilian Michels > Priority: Blocker > Fix For: 2.20.0 > > Time Spent: 7h 10m > Remaining Estimate: 0h > > With the introduction of timer output timestamp, a new watermark hold had > been added to the Flink Runner. The watermark computation works on the keyed > state backend which computes a key-scoped watermark hold and not the desired > operator-wide watermark hold. > Computation: > https://github.com/apache/beam/blob/b564239081e9351c56fb0e7d263495b95dd3f8f3/runners/flink/src/main/java/org/apache/beam/runners/flink/translation/wrappers/streaming/DoFnOperator.java#L1140 > Key-scoped state: > https://github.com/apache/beam/blob/b564239081e9351c56fb0e7d263495b95dd3f8f3/runners/flink/src/main/java/org/apache/beam/runners/flink/translation/wrappers/streaming/DoFnOperator.java#L1130 > We need to change this to operate on all keys. This has to be done before > fixing BEAM-9566. -- This message was sent by Atlassian Jira (v8.3.4#803005)