Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52742587
Hi everyone, thanks for your comments. I have tested the latest commit and
I think this is ready to go in my opinion. I have fixed the PySpark behavior
where the subprocess doesn't actually terminate in a similar way Py4j's
`JavaGateway` handles it (see `--die-on-broken-pipe`, which we currently use
for the direct `SparkSubmit` code path). I have verified that the precedence
order of various driver configs are as expected.
---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
