Github user adamstatdna commented on the issue:
https://github.com/apache/spark/pull/16743
Yes, I believe it is still active. The solution stated by Marcelo of
detecting the exit code in local mode would be a solution for my purposes
of testing where you want to do end-to-end integration testing in local
mode and test for failure/success states of the spark app in question.
On Thu, May 11, 2017 at 7:23 AM, Hyukjin Kwon <[email protected]>
wrote:
> Hi @thomastechs <https://github.com/thomastechs>, is it still active and
> any opinion on ^ ? Otherwise, I would like to propose to close this.
>
> â
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/16743#issuecomment-300804935>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AWX-_EAGX-_x73pKjTHrC8aHf0O_smEyks5r4xnxgaJpZM4LxtgW>
> .
>
---
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]