Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16827
@srowen make sense, close it first before there is a follow-up
---
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/16827
I just don't think that setting properties to override defaults, which is
the common reason this would occur, is a warning or error situation.
---
If your project is set up for it, you can reply to
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16827
@srowen make senses. What about logging a warning/error message if
'spark.master' is set with different values?
---
If your project is set up for it, you can reply to this email and have your
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16827
I still don't see a reason to special-case this property. It also means you
can't override a property set by defaults, which could be a problem.
---
If your project is set up for it, you can reply
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16827
@srowen Could you please take a second review?
cc @rxin also
---
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
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16827
cc @rxin also
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/16827
@srowen Well, this change may be really radical. Just like what I say, many
fresh users has no consciousness to check if job runs correctly in standalone
mode or yarn mode. Maybe, they just forgot
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16827
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72494/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16827
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/16827
**[Test build #72494 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72494/testReport)**
for PR 16827 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16827
I don't think we want or need to special-case behavior of this one
property. It's also a behavior change.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16827
**[Test build #72494 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72494/testReport)**
for PR 16827 at commit
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16827
Working on UT failure.
---
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/16827
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72486/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16827
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/16827
**[Test build #72486 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72486/testReport)**
for PR 16827 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16827
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/16827
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72485/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16827
**[Test build #72485 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72485/testReport)**
for PR 16827 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16827
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/16827
**[Test build #72483 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72483/testReport)**
for PR 16827 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16827
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72483/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16827
**[Test build #72486 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72486/testReport)**
for PR 16827 at commit
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16827
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 wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16827
**[Test build #72485 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72485/testReport)**
for PR 16827 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16827
**[Test build #72483 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72483/testReport)**
for PR 16827 at commit
26 matches
Mail list logo
