Flink runner failing testOnWindowTimestampSkew
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
org.apache.beam.sdk.transforms.ParDoTest$TimestampTests.testOnWindowTimestampSkew
java.lang.AssertionError: noskew/ParMultiDo(OnWindowExpirationTimestampSkewing).output:
Expected: iterable with items ["output1970-01-01T00:00:00.006Z"] in any order
but: not matched: "output1970-01-01T00:00:00.005Z"
Imported from Jira [BEAM-13573](https://issues.apache.org/jira/browse/BEAM-13573). Original Jira may contain additional context.
Reported by: ibzib.
Contributor guide
Research direction
Start by running org.apache.beam.sdk.transforms.ParDoTest$TimestampTests.testOnWindowTimestampSkew with the Flink runner and inspect the timestamp-skew behavior. The issue is resolved when the test produces the expected output timestamp 1970-01-01T00:00:00.006Z instead of 0.005Z.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100