-
Notifications
You must be signed in to change notification settings - Fork 13.8k
[FLINK-23129][docs] Document ApplicationMode limitations #16281
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
|
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit 63b4d23 (Thu Jun 24 13:16:30 UTC 2021) ✅no warnings Mention the bot in a comment to re-run the automated checks. Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. DetailsThe Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commandsThe @flinkbot bot supports the following commands:
|
|
|
||
| Additionaly, when any of multiple running jobs in Application Mode (submitted for example using | ||
| `executeAsync()`) gets cancelled, all jobs will be stopped and the JobManager shuts down. | ||
| Finishing (by the sources shutting down) of any of multiple running jobs is supported. |
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.
I find this a bit unclear, since finishing a job is not an active action triggered by the user. What do you think of something along the lines of "Regular job completions (by the sources shutting down) are supported."?
Co-authored-by: Nicolaus Weidner <nicolaus.weidner@tngtech.com>
|
Thanks a lot for your review. I addressed all your comments. |
Cancelling one of multiple running jobs in AppMode is not properly supported.