Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14020
lgtm. Merging to 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 wishes
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14020
> Will putting that jar in Spark's classpath work? Seems so?
Yes but the whole point of the configuration is to not pollute Spark's
class loader.
---
If your project is set up for it, you
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14020
also cc @marmbrus
---
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 yhuai commented on the issue:
https://github.com/apache/spark/pull/14020
Will putting that jar in Spark's classpath work? Seems so?
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/14020
I'll leave this open until EOD then push the change.
---
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
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14020
I'm not familiar with this part, cc @liancheng to take a look
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/14020
ping
---
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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14020
@cloud-fan @yhuai
---
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,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14020
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61768/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14020
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14020
**[Test build #61768 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61768/consoleFull)**
for PR 14020 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14020
**[Test build #61768 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61768/consoleFull)**
for PR 14020 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14020
Might be a legitimate test failure, will look later.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14020
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/14020
**[Test build #61645 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61645/consoleFull)**
for PR 14020 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14020
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61645/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14020
**[Test build #61645 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61645/consoleFull)**
for PR 14020 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14020
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61640/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14020
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/14020
**[Test build #61640 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61640/consoleFull)**
for PR 14020 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14020
**[Test build #61640 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61640/consoleFull)**
for PR 14020 at commit
21 matches
Mail list logo
