-
Notifications
You must be signed in to change notification settings - Fork 13.8k
[FLINK-3296] Remove 'flushing' behavior of the OutputFormat in DataStream API #1563
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.
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
Conversation
With the |
docs/apis/streaming/index.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May be worth adding that this means usually "at-least-once" , but may also mean data loss in cases where the output formats buffer data and do not immediately persist it.
Code looks good. I would like to update the docs to include a bit more info (like in the inline comment) and at least refer to the |
Changes look good to me |
a2716ea
to
205a79a
Compare
Thank you for the review. I've addressed the comments and rebased the change. Once travis has passed, I'll merge it! |
I think the |
I renamed the method to |
6d9a0cf
to
008a1a7
Compare
I'll merge the PR. |
…f the DataStream API This closes apache#1563
…f the DataStream API This closes apache#1563
Changes Unknown when pulling df49d5b on rmetzger:flink3296 into ** on apache:master**. |
I removed the
FileSinkFunctionByMillis
and removed all themillis
arguments on the writing functions.The whole "buffering" and "flushing" functionality was broken: Elements were kept in an ArrayList and send to the OutputFormat on "flush()". However, the flush was not really called periodically. It was only checked when new records arrived. So when a stream is not having elements for a certain time, the last few elements would just stay in the list until new elements arrive again.