Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-158172457
I still don't see why it's necessary to change the class path of the
client. If you're using Spark with HBase you should change the driver /
executor classpaths, not
Github user SaintBacchus commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-158258804
OK, I close.
---
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 SaintBacchus closed the pull request at:
https://github.com/apache/spark/pull/8918
---
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-148818428
What's the use case for this? If possible I'd rather not introduce new
public facing configurations. Also it might be confusing to the new Spark user
if we have both
Github user SaintBacchus commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-148879845
@andrewor14 as I described in
[JIRA](https://issues.apache.org/jira/browse/SPARK-10766), in yarn-cluster
mode, it's hard to set the class path of the client
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-146390725
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-146390741
Merged build started.
---
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 SaintBacchus commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-146390642
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-146409748
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-146409747
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-146409522
[Test build #43374 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43374/console)
for PR 8918 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-146391749
[Test build #43374 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43374/consoleFull)
for PR 8918 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-143192934
[Test build #43019 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43019/console)
for PR 8918 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-143192978
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-143192975
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-143170183
[Test build #43019 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43019/consoleFull)
for PR 8918 at commit
GitHub user SaintBacchus opened a pull request:
https://github.com/apache/spark/pull/8918
[SPARK-10766][SPARK-SUBMIT]Add some configuration for the client process in
cluster mode.
Add this four configurations for the client only in cluster mode:
* `spark.client.memory` of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-143170062
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-143170043
Merged build triggered.
---
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
19 matches
Mail list logo
