reuvenlax commented on PR #22347: URL: https://github.com/apache/beam/pull/22347#issuecomment-1197293311
The time on the production is always window.maxTimestamp(), which should be in the valid range. On Wed, Jul 27, 2022 at 12:47 PM Kenn Knowles ***@***.***> wrote: > But the timestamp is outside of Beam's allowed range of timestamps. It is > just invalid data, right? Even if there is a short term change that will > get around the current check, it is still bad data. > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/beam/pull/22347#issuecomment-1197291788>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFAYJVMCEPRGFDQSHKIVCHDVWGG35ANCNFSM54BIPKIA> > . > 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]
