Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Completely remove time triggers from batch processing #190

Open
je-ik opened this issue Nov 21, 2017 · 0 comments
Open

Completely remove time triggers from batch processing #190

je-ik opened this issue Nov 21, 2017 · 0 comments

Comments

@je-ik
Copy link
Contributor

je-ik commented Nov 21, 2017 •
edited

Batch processing is not supposed to use time triggering, because the watermark should have only two values - Long.MIN_VALUE while processing any data and Long.MAX_VALUE after completion of the calculation. There is no discrete time in between these two state.
@je-ik je-ik changed the title Completely remove triggers from batch processing Completely remove time triggers from batch processing Nov 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@je-ik