[GitHub] spark pull request #16492: [SPARK-19113][SS][Tests]Set UncaughtExceptionHand...
Github user asfgit closed the pull request at: https://github.com/apache/spark/pull/16492 --- 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
[GitHub] spark pull request #16492: [SPARK-19113][SS][Tests]Set UncaughtExceptionHand...
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/16492#discussion_r95065464
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamTest.scala ---
@@ -235,7 +235,10 @@ trait StreamTest extends QueryTest with
SharedSQLContext with Timeouts {
*/
def testStream(
_stream: Dataset[_],
- outputMode: OutputMode = OutputMode.Append)(actions: StreamAction*):
Unit = {
+ outputMode: OutputMode = OutputMode.Append)(actions: StreamAction*):
Unit = synchronized {
+// `synchronized` is added to prevent the user from calling
`testStream` concurrently because
--- End diff --
Can you elaborate why `StreamingQueryListener` can be used concurrently?
I'm reading the comment: "it does not work because something else does not
work". Why? What's wrong with `StreamingQueryListener`?
---
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
[GitHub] spark pull request #16492: [SPARK-19113][SS][Tests]Set UncaughtExceptionHand...
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/16492#discussion_r95065415
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamSuite.scala ---
@@ -238,7 +238,7 @@ class StreamSuite extends StreamTest {
}
}
- testQuietly("fatal errors from a source should be sent to the user") {
+ testQuietly("handle fatal errors thrown from the stream thread
correctly") {
--- End diff --
`correctly` is superfluous and could be removed.
---
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
[GitHub] spark pull request #16492: [SPARK-19113][SS][Tests]Set UncaughtExceptionHand...
GitHub user zsxwing opened a pull request: https://github.com/apache/spark/pull/16492 [SPARK-19113][SS][Tests]Set UncaughtExceptionHandler in onQueryStarted to ensure catching fatal errors during query initialization ## What changes were proposed in this pull request? StreamTest sets `UncaughtExceptionHandler` after starting the query now. It may not be able to catch fatal errors during query initialization. This PR uses `onQueryStarted` callback to fix it. ## How was this patch tested? Jenkins You can merge this pull request into a Git repository by running: $ git pull https://github.com/zsxwing/spark SPARK-19113 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/16492.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 #16492 commit 080a2698928366e4a17d165cebebf4f44c797f40 Author: Shixiong Zhu Date: 2017-01-06T23:01:04Z Set UncaughtExceptionHandler in onQueryStarted to ensure catching fatal errors during query initialization --- 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
