Github user srowen commented on the issue:
https://github.com/apache/spark/pull/12000
PS @mchalek can you manually close this PR? it's merged but can't be auto
closed
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user zzcclp commented on the issue:
https://github.com/apache/spark/pull/12000
thanks, @mchalek
---
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
Github user zzcclp commented on the issue:
https://github.com/apache/spark/pull/12000
@srowen @mchalek could you open a new pr for master/branch-2.0?
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/12000
OK open a new PR for master
---
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
Github user zzcclp commented on the issue:
https://github.com/apache/spark/pull/12000
Hi, @srowen @JoshRosen @mchalek , this issue still exists on
branch-2.0/master, if I add "driver=com.mysql.jdbc.Driver" property to
write.jdbc's properties params, it was ok, otherwise failed.
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 not
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 srowen commented on the issue:
https://github.com/apache/spark/pull/12000
I had the impression this was specific to the 1.x code, and not an issue in
2.x?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user zzcclp commented on the issue:
https://github.com/apache/spark/pull/12000
@srowen @JoshRosen does this pr need to be merged into master or
branch-2.0 ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12000
Can one of the admins verify this patch?
---
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
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 srowen commented on the issue:
https://github.com/apache/spark/pull/12000
Merged to 1.6 per Josh
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12000
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12000
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59806/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12000
**[Test build #59806 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59806/consoleFull)**
for PR 12000 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12000
**[Test build #59806 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59806/consoleFull)**
for PR 12000 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/12000
Jenkins retest this please
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12000
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59804/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12000
**[Test build #59804 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59804/consoleFull)**
for PR 12000 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12000
Merged build finished. Test FAILed.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12000
**[Test build #59804 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59804/consoleFull)**
for PR 12000 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/12000
Jenkins test this please
---
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
Github user zzcclp commented on the issue:
https://github.com/apache/spark/pull/12000
@srowen @JoshRosen @holdenk could you take a look and merge this pr?
---
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
23 matches
Mail list logo
