Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13115#issuecomment-219436922
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/13115#issuecomment-219436923
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/13115#issuecomment-219436798
**[Test build #58641 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58641/consoleFull)**
for PR 13115 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13115#issuecomment-219427662
**[Test build #58641 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58641/consoleFull)**
for PR 13115 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13115#issuecomment-219213787
(I think it would be nicer if the PR description is fill up.)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13115#issuecomment-219213070
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/13115#issuecomment-219213071
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/13115#issuecomment-219213068
**[Test build #58605 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58605/consoleFull)**
for PR 13115 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13115#issuecomment-219212931
**[Test build #58605 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58605/consoleFull)**
for PR 13115 at commit
Github user KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-219212923
@andrewor14 See https://github.com/apache/spark/pull/13115,
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user KaiXinXiaoLei closed the pull request at:
https://github.com/apache/spark/pull/10900
---
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 KaiXinXiaoLei opened a pull request:
https://github.com/apache/spark/pull/13115
[SPARK-12492] Using spark-sql commond to run query, write the event of
SparkListenerJobStart
See https://github.com/apache/spark/pull/10900
## What changes were proposed in this pull
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-216711577
BY THE WAY this code is all moved into `QueryExecution.scala` now since we
deleted `HiveContext`. It might be easier to just create a new patch
altogether. (see
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-216711282
It's just wrapping the things right? Then this LGTM assuming you didn't
change anything else. @KaiXinXiaoLei please rebase.
---
If your project is set up for it,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-210493191
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/10900#issuecomment-210493184
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/10900#issuecomment-210492856
**[Test build #55929 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55929/consoleFull)**
for PR 10900 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-210476544
**[Test build #55929 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55929/consoleFull)**
for PR 10900 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-208926178
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/10900#issuecomment-208926182
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/10900#issuecomment-208926170
**[Test build #55611 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55611/consoleFull)**
for PR 10900 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-208925742
**[Test build #55611 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55611/consoleFull)**
for PR 10900 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-208455143
> @zsxwing I change it, Thanks.
Did you push?
---
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 KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-208319014
@zsxwing I change it, 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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-207596874
Okey, I found the issue. `executedPlan` is a lazy val. When it's called at
the first time, it may call `stringResult`. So if `executedPlan` is moved into
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-204186561
@andrewor14 Looks executedPlan must be called before calling
`SQLExecution.withNewExecutionId`. Do you know why?
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-204165558
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/10900#issuecomment-204165563
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/10900#issuecomment-204165308
**[Test build #54668 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54668/consoleFull)**
for PR 10900 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-204149427
**[Test build #54668 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54668/consoleFull)**
for PR 10900 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-204148427
LGTM pending tests
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-204147906
retest 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-203484299
**[Test build #54521 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54521/consoleFull)**
for PR 10900 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-203484553
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/10900#issuecomment-203484543
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/10900#issuecomment-203450655
**[Test build #54521 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54521/consoleFull)**
for PR 10900 at commit
Github user KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-203328686
Ok, I will change. 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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-203038434
also cc @zsxwing
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/10900#discussion_r57774278
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveContext.scala ---
@@ -615,11 +615,13 @@ class HiveContext private[hive](
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/10900#discussion_r57774355
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveContext.scala ---
@@ -615,11 +615,13 @@ class HiveContext private[hive](
Github user KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-200819923
@JoshRosen Can u check? 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-174539117
**[Test build #49994 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49994/consoleFull)**
for PR 10900 at commit
GitHub user KaiXinXiaoLei opened a pull request:
https://github.com/apache/spark/pull/10900
[SPARK-12492] Using spark-sql commond to run query, write the event of
SparkListenerJobStart
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-174582170
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-174582176
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/10900#issuecomment-174581473
**[Test build #49994 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49994/consoleFull)**
for PR 10900 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10900#issuecomment-174570726
Can you write a description for this PR to explain the motivation for this
change?
---
If your project is set up for it, you can reply to this email and have your
47 matches
Mail list logo
