Github user MayerRoman closed the pull request at:
https://github.com/apache/flink/pull/3287
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user MayerRoman commented on the issue:
https://github.com/apache/flink/pull/3031
Ok
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user MayerRoman closed the pull request at:
https://github.com/apache/flink/pull/3031
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user MayerRoman commented on the issue:
https://github.com/apache/flink/pull/3031
Hello, Tzu-Li Tai!
I think you make a good decision and agree to the fact that the PR and JIRA
ticket can be closed.
Do not worry about the done work, I got good experience in the
Github user MayerRoman commented on the issue:
https://github.com/apache/flink/pull/3031
I hope that I ended up with another issue, and I come back to this.
First, I want to ask a question that perhaps remove all the others.
Tzu-Li Tai, did I understand correctly that
GitHub user MayerRoman opened a pull request:
https://github.com/apache/flink/pull/3287
[FLINK-4540][yarn] Delayed cluster startup until the job has been fully
assembled, in the case of launching detached jobs
[FLINK-4540] Detached job execution may prevent cluster shutdown
Github user MayerRoman commented on the issue:
https://github.com/apache/flink/pull/3031
Thank you Tzu-Li Tai.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
GitHub user MayerRoman opened a pull request:
https://github.com/apache/flink/pull/3045
[FLINK-5390] [yarn] Fix for proper closing input and output streams, in
case of errors
[FLINK-5390] input should be closed in finally block in
YarnFlinkApplicationMasterRunner#loadJobGraph
Github user MayerRoman commented on the issue:
https://github.com/apache/flink/pull/3031
I think that the changes that I propose eliminates the possibility of
starting with checkpoints created before my code changes.
Because now it saves ListState>> (partition +
GitHub user MayerRoman opened a pull request:
https://github.com/apache/flink/pull/3031
[FLINK-4616] Added functionality through which watermarks for each paâ¦
â¦rtition are saved and loaded via checkpointing mechanism
[FLINK-4616] Kafka consumer doesn't store
Github user MayerRoman commented on the issue:
https://github.com/apache/flink/pull/2865
Please check changes.
I removed the test and add a check in method.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
GitHub user MayerRoman opened a pull request:
https://github.com/apache/flink/pull/2865
[FLINK-5002] Renamed getNumberOfUsedBuffers() method to
bestEffortGetNumOfUsedBuffers(), add a test to check that it does not return a
negative value
[FLINK-5002] Lack of synchronization in
GitHub user MayerRoman opened a pull request:
https://github.com/apache/flink/pull/2862
[FLINK-4741] Fix for the proper shutdown the ServerBootstrap in the process
of stopping the WebRuntumeMonitor
[FLINK-4741] WebRuntimeMonitor does not shut down all of it's th
13 matches
Mail list logo
