diff options
| author | Huaxin Gao <huaxing@oc0558782468.ibm.com> | 2015-12-03 08:42:21 +0000 |
|---|---|---|
| committer | Sean Owen <sowen@cloudera.com> | 2015-12-03 08:42:21 +0000 |
| commit | 5349851f368a1b5dab8a99c0d51c9638ce7aec56 (patch) | |
| tree | 7fe5243b5e288e88b97c1b40cac32572ae71e993 /docs | |
| parent | ec2b6c26c9b6bd59d29b5d7af2742aca7e6e0b07 (diff) | |
| download | spark-5349851f368a1b5dab8a99c0d51c9638ce7aec56.tar.gz spark-5349851f368a1b5dab8a99c0d51c9638ce7aec56.tar.bz2 spark-5349851f368a1b5dab8a99c0d51c9638ce7aec56.zip | |
[SPARK-12088][SQL] check connection.isClosed before calling connection…
In Java Spec java.sql.Connection, it has
boolean getAutoCommit() throws SQLException
Throws:
SQLException - if a database access error occurs or this method is called on a closed connection
So if conn.getAutoCommit is called on a closed connection, a SQLException will be thrown. Even though the code catch the SQLException and program can continue, I think we should check conn.isClosed before calling conn.getAutoCommit to avoid the unnecessary SQLException.
Author: Huaxin Gao <huaxing@oc0558782468.ibm.com>
Closes #10095 from huaxingao/spark-12088.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions