GitHub user tejasapatil opened a pull request:
https://github.com/apache/spark/pull/13834
[TRIVIAL] [CORE] [ScriptTransform] move printing of stderr buffer before
closing the outstream
## What changes were proposed in this pull request?
Currently, if due to some failure, the outstream gets destroyed or closed
and later `outstream.close()` leads to IOException in such case. Due to this,
the `stderrBuffer` does not get logged and there is no way for users to see why
the job failed.
The change is to first display the stderr buffer and then try closing the
outstream.
## How was this patch tested?
The correct way to test this fix would be to grep the log to see if the
`stderrBuffer` gets logged but I dont think having test cases which do that is
a good idea.
(If this patch involves UI changes, please attach a screenshot; otherwise,
remove this)
â¦
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tejasapatil/spark script_transform
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/13834.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13834
----
commit 04c86373e3b259471adef37a2c4aa7650f19134e
Author: Tejas Patil <[email protected]>
Date: 2016-06-22T03:22:33Z
[TRIVIAL] [CORE] [ScriptTransform] move printing of stderr buffer before
closing the outstream
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
