-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
[FLINK-29325][documentation]Fix documentation bug on how to enable ba… #20849
Conversation
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.
Thanks for the contribution, LGTM.
f5138a9
to
e455718
Compare
… for streaming examples
e455718
to
6e8cb1b
Compare
@flinkbot run azure |
The CI on a forked pipeline could pass, and the reason why this CI would fail is due to FLINK-29315. |
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.
Before merging, I think the kernel idea of this doc is to tell users how to submit jar program with batch execution mode via commands. Current WordCount.jar
cannot use such method due to FLINK-24830, however, we should still follow the kernel idea of why this doc exists.
Maybe we can change the line to $ bin/flink run -Dexecution.runtime-mode=BATCH <jarFile>
.
What do you think?
… for streaming examples
I have update the doc as you said |
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.
Thanks for the update! LGTM.
My forked CI passed: https://dev.azure.com/myasuka/flink/_build/results?buildId=436&view=results |
… for streaming examples This closes #20849.
… for streaming examples This closes #20849.
… for streaming examples This closes apache#20849.
What is the purpose of the change
Fix documentation error on how to enable batch mode for streaming examples.
Brief change log
use --execution-mode BATCH instead of -Dexecution.runtime-mode=BATCH
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: (no)Documentation