Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8469
---
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 enab
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135579757
I am merging it to master and branch 1.5.
---
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 d
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135578927
[Test build #1698 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1698/console)
for PR 8469 at commit
[`dead685`](https://github
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135556521
[Test build #1698 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1698/consoleFull)
for PR 8469 at commit
[`dead685`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-13418
[Test build #41705 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41705/console)
for PR 8469 at commit
[`dead685`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-13477
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-13478
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135543732
[Test build #41705 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41705/consoleFull)
for PR 8469 at commit
[`dead685`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135540545
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135540508
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 h
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8469#discussion_r38140769
--- Diff: docs/sql-programming-guide.md ---
@@ -2057,6 +2057,12 @@ options.
- The canonical name of SQL/DataFrame functions are now lower case (e.g.
sum v
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135523908
It works. I will update doc.
---
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135302032
I will test it with my partitioned JSON table.
---
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 proj
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135212281
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135212278
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135211959
[Test build #41650 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41650/console)
for PR 8469 at commit
[`acec3ca`](https://github.
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135207922
LGTM. We should mention this in the release note and migration guide.
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135180058
[Test build #41650 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41650/consoleFull)
for PR 8469 at commit
[`acec3ca`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135178770
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135178750
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 h
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8469#issuecomment-135178078
@liancheng Maybe it is better to make JSON, Parquet, and ORC consistent
instead of fixing JSON's refresh problem.
---
If your project is set up for it, you can reply to t
GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/8469
[SPARK-10287] [SQL] Fixes JSONRelation refreshing on read path
https://issues.apache.org/jira/browse/SPARK-10287
After porting json to HadoopFsRelation, it seems hard to keep the behavior
of
22 matches
Mail list logo
