Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/14419
@HyukjinKwon no worries - just wanted to make sure we weren't accidentally
duplicating eachothers efforts :)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14419
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63051/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14419
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/14419
**[Test build #63051 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63051/consoleFull)**
for PR 14419 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14419
**[Test build #63051 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63051/consoleFull)**
for PR 14419 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14419
No, I don't :). I just meant I wanted to say that this fix is reasonable
and the reason I didn't submit a PR has not been because there is potential
incompatability. It was because just I was
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/14419
@HyukjinKwon do you have a PR for this? If so I can go ahead and close this
one (and lets maybe sync some on the deprecation stuff we are both cleaning up
:))
---
If your project is set up for
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/14419
So yes as @HyukjinKwon says its just in the tests.
I figured this would be ok across the hadoop versions we target because I
looked at the build deps files and they all listed
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14419
Could cc @liancheng who has more insight about thie 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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14419
Yes, actually I took a look for this as well and it seems okay (I was
thinking doing this with other issues).
If my understanding is correct, this would not affect actual writing in
Spark
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14419
Do we know if this works across versions of Parquet that are still in play
for Spark builds? I know we've got some YARN and Scala warnings that we can't
adjust for that reason. Just double checking.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14419
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63039/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14419
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/14419
**[Test build #63039 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63039/consoleFull)**
for PR 14419 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14419
**[Test build #63039 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63039/consoleFull)**
for PR 14419 at commit
15 matches
Mail list logo
