Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9490
---
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 the feature is
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-213668158
ping @zjffdu
---
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
Github user l15k4 commented on the pull request:
https://github.com/apache/spark/pull/9142#issuecomment-194248531
I just upgraded to to hadoop 2.6.4 and Spark 1.6 and I still get :
```
java.io.IOException: No input paths specified in job
at
Github user l15k4 commented on the pull request:
https://github.com/apache/spark/pull/9142#issuecomment-193977981
Hey, does this support hadoop Globs and Wildcards? For which release this
has been fixed? I guess 1.6, right?
---
If your project is set up for it, you can reply to this
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-182785426
Please close this PR
---
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
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-162402210
@yhuai @liancheng any more comments ?
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-162402641
@zjffdu How about we revisit it after we release 1.6?
---
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 zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-162406408
@yhuai Sure, np
---
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160474727
@zjffdu I feel it is not a good idea to change lots of code just to get a
better error message. Is it possible to have a small change to achieve the goal?
---
If your
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160493625
@yhuai Only changing JSONRelation/TextRelation can be a short-term
solution. But since this is a general issue for HadoopFsRelation. so it would
be better to do it in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160172809
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160172679
**[Test build #46821 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46821/consoleFull)**
for PR 9490 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160172813
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160117323
**[Test build #46810 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46810/consoleFull)**
for PR 9490 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160117437
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160117440
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160140929
**[Test build #46821 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46821/consoleFull)**
for PR 9490 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160063909
**[Test build #46809 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46809/consoleFull)**
for PR 9490 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160063912
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160063910
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160066544
**[Test build #46810 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46810/consoleFull)**
for PR 9490 at commit
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160029445
@liancheng sorry for late response, will try to make a new commit this
weekend
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-160063059
**[Test build #46809 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46809/consoleFull)**
for PR 9490 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-159582773
Hey @zjffdu, are you still working on this?
---
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
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/9490#discussion_r44516927
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -604,10 +609,33 @@ abstract class HadoopFsRelation
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155702715
**[Test build #45606 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45606/consoleFull)**
for PR 9490 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155702826
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155713852
Comments for the change:
The case of empty or non-exist inputs is a little tricky. Here's the
several cases I summarize
* Only parse the inputs at execution
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/9490#discussion_r44516708
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -431,7 +436,7 @@ abstract class HadoopFsRelation
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/9490#discussion_r44517000
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -431,7 +436,7 @@ abstract class HadoopFsRelation
Github user zjffdu commented on a diff in the pull request:
https://github.com/apache/spark/pull/9490#discussion_r44534648
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -604,10 +609,33 @@ abstract class HadoopFsRelation
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9490#discussion_r44559693
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -604,10 +609,33 @@ abstract class HadoopFsRelation
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9490#discussion_r44559591
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/json/JSONRelation.scala
---
@@ -93,10 +93,13 @@ private[sql] class JSONRelation(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155702825
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
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/9490#discussion_r44538127
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -604,10 +609,33 @@ abstract class HadoopFsRelation
Github user zjffdu commented on a diff in the pull request:
https://github.com/apache/spark/pull/9490#discussion_r44608884
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -604,10 +609,33 @@ abstract class HadoopFsRelation
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/9490#discussion_r44615417
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -604,10 +609,33 @@ abstract class HadoopFsRelation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155358765
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155358725
**[Test build #45500 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45500/consoleFull)**
for PR 9490 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155358764
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155679162
**[Test build #45606 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45606/consoleFull)**
for PR 9490 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155679059
Merged build started.
---
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 pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155679050
Merged build triggered.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155656214
**[Test build #45590 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45590/consoleFull)**
for PR 9490 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155659345
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155659290
**[Test build #45590 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45590/consoleFull)**
for PR 9490 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155655273
Merged build triggered.
---
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 pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155655285
Merged build started.
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-155325667
test 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
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154340042
Looks like the failed test is not related. @liancheng Please help review
it. Thanks
---
If your project is set up for it, you can reply to this email and have your
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154007286
CC @chenghao-intel
---
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
GitHub user zjffdu opened a pull request:
https://github.com/apache/spark/pull/9490
[SPARK-11102] [SQL] Uninformative exception when specifing non-exist
Rebase the code base and create another PR
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154008528
**[Test build #45111 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45111/consoleFull)**
for PR 9490 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154005153
Merged build started.
---
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 pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154005130
Merged build triggered.
---
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 zjffdu closed the pull request at:
https://github.com/apache/spark/pull/9223
---
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 the feature is
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-154004758
Close it as needs to rebase the code base. Open #9490
---
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 pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154015117
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154015079
**[Test build #45111 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45111/consoleFull)**
for PR 9490 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154015116
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154239731
cc @liancheng
---
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 pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154250434
Merged build triggered.
---
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 pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154262061
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154262062
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154250468
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154262011
**[Test build #45178 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45178/consoleFull)**
for PR 9490 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154250720
**[Test build #45178 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45178/consoleFull)**
for PR 9490 at commit
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-153972020
@chenghao-intel The JsonRelation has another special case that it allow
input paths as empty when it takes RDD[String] as input. So HadoopFsRelation
can not assume all
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-152722643
@zjffdu are you still working on this?
---
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151400091
Probably we also need to add the assertion at:
```scala
class HadoopFsRelation {
...
final private[sql] def buildScan(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151076305
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151076306
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151089248
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151089252
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151084190
**[Test build #44349 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44349/consoleFull)**
for PR 9223 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151080499
Merged build triggered.
---
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 pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151080563
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151089182
**[Test build #44349 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44349/consoleFull)**
for PR 9223 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151070213
Merged build started.
---
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 pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151070148
Merged build triggered.
---
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 zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151336012
SPARK-11274 introduce the same issue in TextRelation. Need to fix it in
TextRelation too. But SPARK-11264 is not in this branch. Should I rebase this
branch and commit
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151336783
That's actually what I mean, this is a general problem of the empty path,
we'd better fix it in one place, I thought we can fix it in the
`fileStatusCache`,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151149139
**[Test build #44353 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44353/consoleFull)**
for PR 9223 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151149341
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151149345
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151127094
Merged build triggered.
---
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 pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151127117
Merged build started.
---
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 pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151138439
Merged build triggered.
---
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 pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151138486
Merged build started.
---
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 pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151142783
Merged build triggered.
---
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 pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151142837
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151144593
**[Test build #44354 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44354/consoleFull)**
for PR 9223 at commit
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151143545
Still put the input paths checking in JsonRelation. Because there's still
some cases that is valid for empty input. e.g. when creating a table based on
an empty
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151135023
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151129780
**[Test build #44352 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44352/consoleFull)**
for PR 9223 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151134946
**[Test build #44352 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44352/consoleFull)**
for PR 9223 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151135028
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151140813
**[Test build #44353 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44353/consoleFull)**
for PR 9223 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151182635
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-151182244
**[Test build #44354 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44354/consoleFull)**
for PR 9223 at commit
1 - 100 of 138 matches
Mail list logo
