GitHub user tribbloid reopened a pull request:
https://github.com/apache/spark/pull/8785
[Spark-10625] [SQL] Spark SQL JDBC read/write is unable to handle JDBC
Drivers that adds unserializable objects into connection properties
Connection properties are now deep copied before they are used by JDBC
Drivers, this solvs all problems in unit tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Schedule1/spark SPARK-10625
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/8785.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 #8785
----
commit 267afca7caa3e06a0fdac123f8a50033a726c564
Author: tribbloid <[email protected]>
Date: 2015-09-15T23:02:57Z
test case demonstrating SPARK-10625:
Spark SQL JDBC read/write is unable to handle JDBC Drivers that adds
unserializable objects into connection properties
add one more unit test
fix JDBCRelation & DataFrameWriter to pass all tests
revise scala style
put driver replacement code into a shared function
fix styling
upgrade to master and resolve all related issues
commit cd641c01260eeabe910d819fffd9193461b37946
Author: tribbloid <[email protected]>
Date: 2015-12-10T01:15:18Z
remove the useless second deep copy of properties
rename test names to be more explicit
commit d33dc9c773e01695b3098f5a69733eacc2a88456
Author: tribbloid <[email protected]>
Date: 2015-12-16T02:39:37Z
minor refactoring based on Sean's suggestion
commit 1dcede3d98575152dda1c46b263fc4e2361f0766
Author: tribbloid <[email protected]>
Date: 2015-12-16T15:37:04Z
move JavaConverters import to under object
commit d2723c8a59301419af6132e06cacbb2860968c71
Author: tribbloid <[email protected]>
Date: 2015-12-21T19:07:05Z
remove the redundant toSeq and pull up lines in brackets
commit 6af8fd8b824f5f343a01868560b74a1f55acd02f
Author: tribbloid <[email protected]>
Date: 2015-12-28T02:05:00Z
improve styling in UnserializableDriverHelper and JDBCRelation
----
---
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]
