Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15382
Merged to 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 wishes so,
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15382
I think this would have to go into 2.0.x as I think it's a regression from
2.0.0, in that the default location moved from a local file to HDFS for many
users, and, it's an HDFS path that can't be cre
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15382
cc @yhuai
---
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
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15382
Great. Is it going to 2.0.x, too?
---
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
ena
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15382
LGTM. This should restore the behavior pre- 11a6844 and be compatible with
Windows.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15382
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15382
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67191/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #67191 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67191/consoleFull)**
for PR 15382 at commit
[`69c5383`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #67191 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67191/consoleFull)**
for PR 15382 at commit
[`69c5383`](https://github.com/apache/spark/commit/6
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15382
@vanzin this may be more like what you're suggesting. I think the Windows
issue makes this a little bit more complex than what you're describing but I
think this ends up being workable.
@avu
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15382
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66810/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15382
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/15382
**[Test build #66810 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66810/consoleFull)**
for PR 15382 at commit
[`ef7a141`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #66810 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66810/consoleFull)**
for PR 15382 at commit
[`ef7a141`](https://github.com/apache/spark/commit/e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #3322 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3322/consoleFull)**
for PR 15382 at commit
[`71f124a`](https://github.com/apache/spark/commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #3322 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3322/consoleFull)**
for PR 15382 at commit
[`71f124a`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #3314 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3314/consoleFull)**
for PR 15382 at commit
[`71f124a`](https://github.com/apache/spark/commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #3314 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3314/consoleFull)**
for PR 15382 at commit
[`71f124a`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #3310 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3310/consoleFull)**
for PR 15382 at commit
[`71f124a`](https://github.com/apache/spark/commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #3310 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3310/consoleFull)**
for PR 15382 at commit
[`71f124a`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15382
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/15382
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66580/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #66580 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66580/consoleFull)**
for PR 15382 at commit
[`71f124a`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #66580 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66580/consoleFull)**
for PR 15382 at commit
[`71f124a`](https://github.com/apache/spark/commit/7
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15382
OK, now using `Utils.resolveURI`. This means all inputs without a scheme
resolve as `file:` URIs, including the default "spark-warehouse". This will
continue to resolve to the local working dir by de
Github user koertkuipers commented on the issue:
https://github.com/apache/spark/pull/15382
i don't think there is such a thing as a HDFS working directory, but that
probably means it just uses the home dir on hdfs (/user/) for any
relative paths
---
If your project is set up for it
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15382
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/15382
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66501/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #66501 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66501/consoleFull)**
for PR 15382 at commit
[`cd4b4b9`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15382
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/15382
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66500/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #66500 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66500/consoleFull)**
for PR 15382 at commit
[`67c2b58`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #66501 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66501/consoleFull)**
for PR 15382 at commit
[`cd4b4b9`](https://github.com/apache/spark/commit/c
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15382
Update on my thinking:
Docs say the default should be "spark-warehouse" in the local working
directory. The original code did establish a default on the local file
system... though in the ho
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #66500 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66500/consoleFull)**
for PR 15382 at commit
[`67c2b58`](https://github.com/apache/spark/commit/6
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15382
Good point. The docs all say it should be working dir, so I was following
the apparent intent along the way here. I don't know if one is more surprising
than the other.
---
If your project is set
Github user koertkuipers commented on the issue:
https://github.com/apache/spark/pull/15382
i think working dir makes more sense than home dir. but could this catch
people by surprise because we now expect write permission in the working dir?
---
If your project is set up for it, you
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #66459 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66459/consoleFull)**
for PR 15382 at commit
[`4fb0e58`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15382
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/15382
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66459/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15382
**[Test build #66459 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66459/consoleFull)**
for PR 15382 at commit
[`4fb0e58`](https://github.com/apache/spark/commit/4
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15382
CC @vanzin -- I think your solution at
https://github.com/apache/spark/pull/13868#discussion_r82252926 is better, will
probably switch to it.
CC @avulanov and @koertkuipers
---
If your pr
42 matches
Mail list logo
