Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3232
I will now try this out and merge it if it workds.
---
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 fe
Github user GEOFBOT commented on the issue:
https://github.com/apache/flink/pull/3232
Resolved merge conflicts
---
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 GEOFBOT commented on the issue:
https://github.com/apache/flink/pull/3232
> It may have worked with a smaller file, but there may be issues with
heavier jobs.
How silly of me. This problem had nothing to do with this pull request,
with YARN, with issues in Flink,
Github user GEOFBOT commented on the issue:
https://github.com/apache/flink/pull/3232
It may have worked with a smaller file, but there may be issues with
heavier jobs. When I ran a more computationally intensive and time consuming
job, the first job of the Python file ran successfull
Github user GEOFBOT commented on the issue:
https://github.com/apache/flink/pull/3232
In the process of getting a more complex job to run, I've tested a basic
multi-job file (seen below) on an Amazon EMR YARN cluster and it works
successfully.
```
from flink.plan.Environm
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3232
Yes, please continue to comment after pushing changes :)
I'll have to try this out on a cluster to be certain, but from the looks of
it this is good to merge.
---
If your project is set up f
Github user GEOFBOT commented on the issue:
https://github.com/apache/flink/pull/3232
Thanks for the comments, I've addressed them with the latest commit.
---
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 do
