Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3718#issuecomment-67806102
@marmbrus Maybe I missed something here, but why do we prefer
`setJobDescription` over `setJobGroup`, especially when the former is
deprecated?
@scwf For job cancellation/stopping, under which shell did you try
`CTRL-C`? Beeline doesn't install a proper signal handler, thus `CTRL-C` simply
kills beeline without stopping/canceling any running job. Actually there is a
signal handler for JDBC statement cancellation, but it's [commented out] [1] in
beeline code. If you were trying spark-sql or spark-shell scripts, a `CTRL-C`
kills the main `SparkContext`, thus all statements are stopped by force.
Would like to add that there is a known job description issue related to
CTAS statements, see [SPARK-2472] [2]. This PR shares exactly the same issue.
Main point of SPARK-2472 quoted below:
> ... The reason is that InsertIntoHiveTable.execute() submits a job to
perform the insertion eagerly at the end of the query planning phase. At that
time, the job description hasn't been updated, thus shows the previous one.
[1]:
https://github.com/apache/hive/blob/release-0.13.1/beeline/src/java/org/apache/hive/beeline/BeeLine.java#L380-L390
[2]: https://issues.apache.org/jira/browse/SPARK-2472
---
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]
