Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18901
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
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18901
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80559/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18901
**[Test build #80559 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80559/testReport)**
for PR 18901 at commit
Github user caneGuy commented on the issue:
https://github.com/apache/spark/pull/18901
All right, i will close this pr.Thanks for your time @vanzin @jerryshao
@tgravescs .
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18901
As Tom suggested, if you add hbase to your gateway's Spark installation,
you won't need to download it every time you submit an application.
This change, the way it is, is really not
Github user caneGuy commented on the issue:
https://github.com/apache/spark/pull/18901
i execute `mvn checkstyle:checkstyle` locally with success status, but i
can not find more logs in jenkins since i want to find which file failed with
style check.
---
If your project is set up
Github user caneGuy commented on the issue:
https://github.com/apache/spark/pull/18901
Yes i have a workaround solution,such as add local jar in "--jars".But i do
not think this is a very edge case.
---
If your project is set up for it, you can reply to this email and have your
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18901
If this is a common problem for your users why not just install the hbase
jars on the launcher box?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18901
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80562/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18901
**[Test build #80562 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80562/testReport)**
for PR 18901 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18901
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/18901
**[Test build #80562 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80562/testReport)**
for PR 18901 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18901
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18901
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80561/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18901
**[Test build #80561 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80561/testReport)**
for PR 18901 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18901
**[Test build #80561 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80561/testReport)**
for PR 18901 at commit
Github user caneGuy commented on the issue:
https://github.com/apache/spark/pull/18901
But i think this case should be fixed since many users of our inner branch
has suffered from this problem.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user caneGuy commented on the issue:
https://github.com/apache/spark/pull/18901
@vanzin i have also thought about what you mentioned above.But since i do
not have enough background knowledge ,i can not think about how to check user
need hbase class first.And my original idea
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18901
**[Test build #80559 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80559/testReport)**
for PR 18901 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18901
I am not a fan of this change. It makes submission unnecessarily more
expensive for everybody to fix an edge case.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18901
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80542/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18901
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/18901
**[Test build #80542 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80542/testReport)**
for PR 18901 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18901
Note I'll file a separate jira for this but even in client mode it will
download and then reupload the file to hdfs for yarn mode, thus defeating the
purpose of it being in hdfs.
---
If your
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18901
Generally its expected that where you launch your job from has all the
necessary jars already, thus all the jar would be available for the Client.
here we download all jars that the user
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18901
**[Test build #80542 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80542/testReport)**
for PR 18901 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18901
ok to test
---
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 caneGuy commented on the issue:
https://github.com/apache/spark/pull/18901
@vanzin take a look at this pr?Thanks.
---
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 jerryshao commented on the issue:
https://github.com/apache/spark/pull/18901
LGTM generally, CC @vanzin to review.
---
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 jerryshao commented on the issue:
https://github.com/apache/spark/pull/18901
Can you please add a unit test to verify the classpath with your changes?
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18901
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
31 matches
Mail list logo
