[
https://issues.apache.org/jira/browse/SPARK-10001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154885#comment-15154885
]
Ryan Blue commented on SPARK-10001:
-----------------------------------
bq. I . . . am uneasy about adopting unusual semantics for a standard signal,
which should rightly kill the shell by default.
I just checked nodejs, python, and irb (ruby) and the behavior in all three is
to return execution to the shell's prompt, not to exit. I think that makes
sense since it basically mimics a normal bash shell. I agree with Jon that it
would be a nice feature, though I would rather get the current patch in and
address the new suggestion in a follow up issue.
[~tri...@gmail.com], could you open a follow-up issue that outlines the
behavior you suggest?
> Allow Ctrl-C in spark-shell to kill running job
> -----------------------------------------------
>
> Key: SPARK-10001
> URL: https://issues.apache.org/jira/browse/SPARK-10001
> Project: Spark
> Issue Type: Improvement
> Components: Spark Shell
> Affects Versions: 1.4.1
> Reporter: Cheolsoo Park
> Priority: Minor
>
> Hitting Ctrl-C in spark-sql (and other tools like presto) cancels any running
> job and starts a new input line on the prompt. It would be nice if
> spark-shell also can do that. Otherwise, in case a user submits a job, say he
> made a mistake, and wants to cancel it, he needs to exit the shell and
> re-login to continue his work. Re-login can be a pain especially in Spark on
> yarn, since it takes a while to allocate AM container and initial executors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
