Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16089
Merging in master. 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
enabled and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16089
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16089
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69519/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16089
**[Test build #69519 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69519/consoleFull)**
for PR 16089 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16089
**[Test build #69519 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69519/consoleFull)**
for PR 16089 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16089
@srowen yea the hadoop format api is pretty awkward to use, and actually
makes everything more complicated than needed.
---
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/16089
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69488/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16089
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/16089
**[Test build #69488 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69488/consoleFull)**
for PR 16089 at commit
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/16089
I ask about committers as I'm staring at the V1 and V2 committer APIs right
now related to S3 destinations; not directly related to this though.
---
If your project is set up for it, you can
Github user NathanHowell commented on the issue:
https://github.com/apache/spark/pull/16089
@steveloughran Spark is handling the output committing somewhere further up
the stack. The path being passed in to `OutputWriterFactory.newInstance` is to
a temporary file, such as
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/16089
AFAIK, the big thing the FileOutputFormat really adds is not the
compression, but the output committer and the stuff to go with that (working
directories, paths, etc etc). If you aren't going
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16089
**[Test build #69488 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69488/consoleFull)**
for PR 16089 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16089
I was going to say, hm, are we sure we want to reimplement / go around the
Hadoop support for this? but in practice it looks like it actually simplifies
some things. At the moment I can't think of
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16089
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69457/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16089
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/16089
**[Test build #69457 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69457/consoleFull)**
for PR 16089 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16089
**[Test build #69457 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69457/consoleFull)**
for PR 16089 at commit
Github user NathanHowell commented on the issue:
https://github.com/apache/spark/pull/16089
Doh, forgot to run the Hive tests. Should be fixed now.
---
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 issue:
https://github.com/apache/spark/pull/16089
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/16089
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69449/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16089
**[Test build #69449 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69449/consoleFull)**
for PR 16089 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16089
**[Test build #69449 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69449/consoleFull)**
for PR 16089 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16089
Jenkins, this is 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
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16089
Yea then this is definitely fine.
---
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 NathanHowell commented on the issue:
https://github.com/apache/spark/pull/16089
Yep. It uses the Hadoop `FileSystem` class to open files, just like
`TextOutputFormat` does.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16089
Does this work against file systems with HDFS API (not local posix)? If
yes, sounds good!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user NathanHowell commented on the issue:
https://github.com/apache/spark/pull/16089
This touches a fair number of components. I also haven't done any
performance testing to see what the impact of this is. Curious what your
thoughts are?
cc/ @marmbrus @rxin @JoshRosen
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16089
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
29 matches
Mail list logo
