apache/beam

OutputTimeFn maybe should be allowed to move elements back in time

Open

#18,119 opened on Jun 3, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (4,097 forks)batch import
P3bugcoregood first issuerunners

Repository metrics

Stars
 (7,313 stars)
PR merge metrics
 (Avg merge 6d) (243 merged PRs in 30d)

Description

EG in this flink failure

https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Flink/org.apache.beam$beam-runners-flink_2.10/1749/testReport/junit/org.apache.beam.sdk.transforms.windowing/WindowTest/testNoWindowFnDoesNotReassignWindows/

Caused by: java.lang.IllegalStateException: OutputTimeFn moved element from 1970-01-01T00:00:00.015Z to earlier time 1970-01-01T00:00:00.009Z for window [1970-01-01T00:00:00.005Z..1970-01-01T00:00:00.010Z)

Imported from Jira BEAM-1553. Original Jira may contain additional context. Reported by: tgroh.

Contributor guide

Research direction
Inspect the failing test and trace the handler path in OutputTimeFn to understand why it allows moving elements to earlier times.
Tech stack
java
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaBeam basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40