Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15117
Sure, I just merged it to 2.0 and resolved the conflict because that was
straightforward here.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15117
I merged this in master but there's a conflict with branch-2.0. Can you
create a patch for 2.0?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15117
LGTM - merging in master/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 not have this feature
enabled and wis
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15117
**[Test build #65484 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65484/consoleFull)**
for PR 15117 at commit
[`5c9e486`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15117
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65484/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15117
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15117
**[Test build #65484 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65484/consoleFull)**
for PR 15117 at commit
[`5c9e486`](https://github.com/apache/spark/commit/5
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15117
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15117
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65482/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15117
**[Test build #65482 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65482/consoleFull)**
for PR 15117 at commit
[`0627254`](https://github.com/apache/spark/commit/
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15117
Hi @srowen, I support this PR and it's a super minor but would this be
sensible if we re-indent child elements in the XML?
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15117
**[Test build #65482 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65482/consoleFull)**
for PR 15117 at commit
[`0627254`](https://github.com/apache/spark/commit/0
12 matches
Mail list logo
