Github user huaxingao commented on the pull request:
https://github.com/apache/spark/pull/10095#issuecomment-161219510
I guess I don't need to provide a regression test. Currently, in JDBCSuite,
there are lots of Warning as the following, the Warning will be gone after the
fix.
13:11:51.738 WARN org.apache.spark.sql.execution.datasources.jdbc.JDBCRDD:
Exception closing connection
org.h2.jdbc.JdbcSQLException: The object is already closed [90007-183]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1466)
at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1444)
at org.h2.jdbc.JdbcConnection.getAutoCommit(JdbcConnection.java:447)
---
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
