Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14030
**[Test build #61659 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61659/consoleFull)**
for PR 14030 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14028
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61657/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14028
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/14028
**[Test build #61657 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61657/consoleFull)**
for PR 14028 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14028
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/14028
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61656/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14028
**[Test build #61656 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61656/consoleFull)**
for PR 14028 at commit
Github user zasdfgbnm commented on the issue:
https://github.com/apache/spark/pull/14027
OK, but will the status of the original JIRA keep being "won't fix", if
someone decide to reopen the discussion on it?
Can anyone give a comment on whether the running on foreground feature
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14017
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14029
**[Test build #61658 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61658/consoleFull)**
for PR 14029 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14017
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14015
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/14015
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 opened a pull request:
https://github.com/apache/spark/pull/14029
[MINOR] [DOCS] Remove unused images; crush PNGs that could use it for good
measure
## What changes were proposed in this pull request?
Coincidentally, I discovered that a couple images
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14027
I'm suggesting you keep the conversation together with the original JIRA,
at least. I don't know if it was going to be merged or not, but it was not
updated by the author in any event.
---
If your
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/3881
It's right there at
https://github.com/apache/spark/pull/3881#issuecomment-113860838
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user zasdfgbnm commented on the issue:
https://github.com/apache/spark/pull/3881
Can anyone explain what happened to this PR? Why people close this PR
without adding any support for running in foreground?
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14028
**[Test build #61657 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61657/consoleFull)**
for PR 14028 at commit
Github user zasdfgbnm commented on the issue:
https://github.com/apache/spark/pull/14027
I followed that PR (https://github.com/apache/spark/pull/3881)
"I was under the impression all the shell scripts were getting refactored
and that this patch had become obsolete. I agree it's
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14028
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/14028
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61654/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14028
**[Test build #61654 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61654/consoleFull)**
for PR 14028 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14028
**[Test build #61656 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61656/consoleFull)**
for PR 14028 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14028
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61653/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14028
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/14028
**[Test build #61653 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61653/consoleFull)**
for PR 14028 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14027
Please don't open a duplicate JIRA. You can see the discussion on the
previous issue and JIRA, which is WontFix, mostly because it ultimately wasn't
followed up on. It's not out of the quesiton but
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13984
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/13984
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61655/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13984
**[Test build #61655 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61655/consoleFull)**
for PR 13984 at commit
Github user zasdfgbnm commented on the issue:
https://github.com/apache/spark/pull/14027
I see similar pull request here:
https://github.com/apache/spark/pull/3881
But I didn't get what happened to that and why it was closed without adding
any support for running in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13984
**[Test build #61655 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61655/consoleFull)**
for PR 13984 at commit
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/13984#discussion_r69377881
--- Diff: R/pkg/R/SQLContext.R ---
@@ -744,6 +746,9 @@ read.df.default <- function(path = NULL, source = NULL,
schema = NULL, ...) {
if
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/13517#discussion_r69377675
--- Diff:
sql/catalyst/src/main/antlr4/org/apache/spark/sql/catalyst/parser/SqlBase.g4 ---
@@ -45,11 +45,11 @@ statement
| ALTER DATABASE
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14028
BTW, this approach can be applied to reading in JSON and CSV as well if
this change is appropriate. I will work on them if this change is sensible and
can be merged.
---
If your project is
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14028
**[Test build #61654 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61654/consoleFull)**
for PR 14028 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14027
(I think It might be nicer if this contribution follows
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark)
---
If your project is set up for it, you can reply to this
Github user krishnakalyan3 commented on the issue:
https://github.com/apache/spark/pull/13894
@holdenk @MLnick is the current update okay?
---
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 WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/14025
cc @srowen
---
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
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/14015
Merge conflicts have been solved.
cc @srowen
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14015
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/14015
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61652/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14015
**[Test build #61652 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61652/consoleFull)**
for PR 14015 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14028
**[Test build #61653 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61653/consoleFull)**
for PR 14028 at commit
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/14028
[SPARK-16351][SQL] Avoid record-per type dispatch in JSON when writing
## What changes were proposed in this pull request?
Currently, `JacksonGenerator.apply` is doing type-based
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14015
**[Test build #61652 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61652/consoleFull)**
for PR 14015 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14027
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
GitHub user zasdfgbnm opened a pull request:
https://github.com/apache/spark/pull/14027
Spark daemon run.sh
## What changes were proposed in this pull request?
I add some shell scripts to support running master and slave foreground,
which makes it more convenient to write
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13911
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61651/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13911
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/13911
**[Test build #61651 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61651/consoleFull)**
for PR 13911 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14010
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/14010
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14026
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61649/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14026
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/14026
**[Test build #61649 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61649/consoleFull)**
for PR 14026 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13984
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/13984
**[Test build #61650 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61650/consoleFull)**
for PR 13984 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13984
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61650/
Test PASSed.
---
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/14021
LGTM
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13911
**[Test build #61651 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61651/consoleFull)**
for PR 13911 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13984
**[Test build #61650 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61650/consoleFull)**
for PR 13984 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13976
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/13976
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61647/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13976
**[Test build #61647 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61647/consoleFull)**
for PR 13976 at commit
101 - 165 of 165 matches
Mail list logo
