reuvenlax commented on issue #22188: URL: https://github.com/apache/beam/issues/22188#issuecomment-1186396794
We expect this to be fixed in 2.40.1 - unfortunately we did not find this bug before 2.40.0 was released. On Fri, Jul 15, 2022 at 2:47 AM Anish Kumar Sarangi < ***@***.***> wrote: > Hi , We are facing this issue with Apache Beam 2.40.0 and also on 2.39, is > it something to be fixed in next release? Adding Logs here for reference-: > java.lang.IllegalStateException: TimestampCombiner moved element from > 294247-01-10T04:00:54.775Z (TIMESTAMP_MAX_VALUE) to earlier time > 294247-01-09T04:00:54.775Z (end of global window) for window > ***@***.*** -: 2.39.0. > And on 2.40.0 Following error is experienced, is it something which will > also get fixed?-: > LOG-: java.lang.IllegalArgumentException: Cannot output with timestamp > 294247-01-10T04:00:54.776Z. Output timestamps must be no earlier than the > timestamp of the current input or timer (294247-01-10T04:00:54.776Z) minus > the allowed skew (0 milliseconds) and no later than > 294247-01-10T04:00:54.775Z. See the DoFn#getAllowedTimestampSkew() Javadoc > for details on changing the allowed skew. > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/beam/issues/22188#issuecomment-1185374497>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFAYJVIMZ7SP77T4LX5FFDLVUEXSNANCNFSM526KATWA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
