GitHub user mchalek opened a pull request:
https://github.com/apache/spark/pull/14420
[SPARK-14204] [SQL] register driverClass rather than user-specified class
This is a pull request that was originally merged against branch-1.6 as
#12000, now being merged into master as well
Github user mchalek commented on the issue:
https://github.com/apache/spark/pull/12000
Ah, the hash for the relevant commit on master is 6c83d93
---
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
Github user mchalek commented on the issue:
https://github.com/apache/spark/pull/12000
The problem is with commit 7f37c1e, so if that commit is on master then
this needs to be merged into master as well. Taking a quick look at the
affected file, it does appear that the incorrect
Github user mchalek commented on the issue:
https://github.com/apache/spark/pull/12000
Cool, thanks for pushing on this @zzcclp and for merging it @srowen. Any
idea when 1.6.2 will be released?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user mchalek commented on the pull request:
https://github.com/apache/spark/pull/12000#issuecomment-205840895
Bump. Would be nice to get closure on this. I doubt that we were in the
minority in being affected by this (although admittedly, complaints of other
failures seem
Github user mchalek commented on the pull request:
https://github.com/apache/spark/pull/12000#issuecomment-203062954
Thanks @holdenk I agree about the value of a regression test for this. I'm
not familiar with how Spark's regression testing works. Is there a mechanism
through which
GitHub user mchalek opened a pull request:
https://github.com/apache/spark/pull/12000
[SPARK-14204] [SQL] register driverClass rather than user class
This pull request fixes an issue in which cluster-mode executors fail to
properly register a JDBC driver when the driver is provided
