GitHub user ckadner opened a pull request:
https://github.com/apache/spark/pull/9345
[SPARK-10890][SQL] don't log expected JdbcSQLException during incompatible
Insert test
The `org.h2.jdbc.JdbcSQLException` is logged by
`org.apache.spark.executor.Executor` and again by
`org.apache.spark.scheduler.TaskSetManager`, so we would need to influence
their log behavior / log levels.
Absent any properties or API to do that, the easiest way to suppress the
logging of the expected exception is to temporarily increase the log threshold
to `FATAL` while the test case is executed and restore the original log level
right after. This could be done globally `org.apache.log4j.RootLogger` or just
for `org.apache.spark.executor.Executor` and
`org.apache.spark.scheduler.TaskSetManager`
I realize this is a _"hack"_ with the side effect of suppressing any other
log message of less than FATAL severity during the test case execution.
Discussion invited :-)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ckadner/spark SPARK-10890
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/9345.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 #9345
----
commit 470fd09b1de528225e1673621a14b332ae1e6e0b
Author: Christian Kadner <[email protected]>
Date: 2015-10-29T01:23:20Z
[SPARK-10890][SQL] don't log expected JdbcSQLException during incompatible
Insert test
----
---
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]
