Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/2759#issuecomment-58746696
+1 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
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/2762#discussion_r18741363
--- Diff:
sql/hive/compatibility/src/test/scala/org/apache/spark/sql/hive/execution/HiveCompatibilitySuite.scala
---
@@ -578,6 +578,7 @@ class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2762#issuecomment-58748067
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21645/consoleFull)
for PR 2762 at commit
GitHub user willb opened a pull request:
https://github.com/apache/spark/pull/2768
SPARK-2863: [SQL] Add facilities for function-argument coercion
This commit adds the `SignedFunction` trait and modifies the `Sqrt`
expression
class to use it for coercing its argument to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2768#issuecomment-58748502
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2768#issuecomment-58748576
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21646/consoleFull)
for PR 2768 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2762#issuecomment-58748909
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21645/consoleFull)
for PR 2762 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2762#issuecomment-58748912
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/2768#issuecomment-58749850
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/2768#issuecomment-58749849
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21646/consoleFull)
for PR 2768 at commit
Github user DeathByTape closed the pull request at:
https://github.com/apache/spark/pull/2769
---
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
GitHub user DeathByTape opened a pull request:
https://github.com/apache/spark/pull/2769
Stats collection
Implementation of basic stats collection for updated scheduler.
You can merge this pull request into a Git repository by running:
$ git pull
Github user DeathByTape commented on the pull request:
https://github.com/apache/spark/pull/2769#issuecomment-58750992
Wrong 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 feature
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/2524#issuecomment-58754077
ping
---
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
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-58754084
ping
---
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
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-58754089
ping
---
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
GitHub user wangxiaojing opened a pull request:
https://github.com/apache/spark/pull/2770
[spark-3907][sql] add truncate table support
JIRA issue: [SPARK-3907]https://issues.apache.org/jira/browse/SPARK-3907
add turncate table support
TRUNCATE TABLE table_name [PARTITION
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2771#issuecomment-58754914
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
GitHub user chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/2771
[SPARK-3911] [SQL] HiveSimpleUdf can not be optimized in constant folding
```
explain extended select cos(null) from src limit 1;
```
outputs:
```
Project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2770#issuecomment-58754916
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2770#issuecomment-58754918
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2771#issuecomment-58755001
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21647/consoleFull)
for PR 2771 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2771#issuecomment-58756581
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21647/consoleFull)
for PR 2771 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2771#issuecomment-58756583
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2759#issuecomment-58759299
This looks good to me. 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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/2759
---
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 sryza commented on the pull request:
https://github.com/apache/spark/pull/2746#issuecomment-58759844
Awesome, sounds good, will hold off.
---
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 sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/2746#discussion_r18743600
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/ExecutorScalingManager.scala ---
@@ -0,0 +1,324 @@
+/*
+ * Licensed to the Apache Software
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2761#issuecomment-58759963
It would be neat if there was some way to restrict the style checker to
only check new/changed lines introduced by a PR. This could be hard to
integrate with local
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2766#issuecomment-58760169
This looks good to me; thanks! I'm happy to merge this PR, but I fear that
we're going to continue this cycle of re-introducing and fixing doctest /
Sphinx problems
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2766
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2751#issuecomment-58760669
Hi @shijinkui, can you provide some motivation / context for this change?
The scheduler is a complicated piece of code and even simple changes like this
can have
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58760768
That particular Flume test is known to be flaky; I think that TD is working
on a rewrite / fix for that test suite.
---
If your project is set up for it, you can
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2712#discussion_r18743728
--- Diff: core/src/test/scala/org/apache/spark/SparkContextSuite.scala ---
@@ -0,0 +1,39 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF)
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58760950
It looks like the original implementation of this converter was added in
2604939f643bca125f5e2fb53e3221202996d41b, all the way back in 2011, so I
believe that this
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58761280
Actually, I don't think that this is a bug. Instead, I think that the
behavior that you're seeing could be an instance of
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58761660
Actually, ignore my earlier (deleted) comments; this looks like a valid
issue (see [HADOOP-6298: BytesWritable#getBytes is a bad name that leads to
programming
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2712#discussion_r18743890
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -1409,7 +1410,9 @@ object SparkContext extends Logging {
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58761838
This looks good to me; sorry for my earlier confusion. If you add a
comment and change the name of the test, I'll merge this and cherry-pick it
back into `branch-1.1`
GitHub user ravipesala opened a pull request:
https://github.com/apache/spark/pull/2772
[SPARK-3814][SQL] Bitwise does not work in Hive
Currently there is no support of Bitwise , | in Spark HiveQl and Spark
SQL as well. So this PR support the same.
I am closing
Github user ravipesala commented on the pull request:
https://github.com/apache/spark/pull/2736#issuecomment-58765712
Since this PR has conflicts , I created new PR
https://github.com/apache/spark/pull/2772 and handled review comments in it.
---
If your project is set up for it, you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2772#issuecomment-58765716
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2772#issuecomment-58765710
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
Github user ravipesala closed the pull request at:
https://github.com/apache/spark/pull/2736
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1839#issuecomment-58765937
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21648/consoleFull)
for PR 1839 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1839#issuecomment-58767530
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/1839#issuecomment-58767527
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21648/consoleFull)
for PR 1839 at commit
Github user james64 commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58767976
Sorry for the test name. Now it should be all fine including commets.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58768088
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21649/consoleFull)
for PR 2712 at commit
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/2773
[SPARK-3912][Streaming] Fixed flakyFlumeStreamSuite
@harishreedharan @pwendell
See JIRA for diagnosis of the problem
https://issues.apache.org/jira/browse/SPARK-3912
The solution was
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58769371
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21649/consoleFull)
for PR 2712 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58769373
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2761#issuecomment-58769389
I quite like standardizing style, but doesn't this have the same problem
mentioned before, that it's going to break a lot of potential merge commits?
When I
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2773#issuecomment-58769438
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21650/consoleFull)
for PR 2773 at commit
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2757#issuecomment-58769459
Wow, there are a lot of changes in this PR. Perhaps this was the most
ignored style rule, eh?
cc @pwendell
---
If your project is set up for it, you can
Github user cocoatomo commented on the pull request:
https://github.com/apache/spark/pull/2766#issuecomment-58769648
Thank you for the comment.
I'm also happy that Jenkins checks this kind of issue rather than me.
-W option of sphinx-build would help us to check and report
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2773#issuecomment-58770568
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/2773#issuecomment-58770566
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21650/consoleFull)
for PR 2773 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2753#issuecomment-58771033
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21651/consoleFull)
for PR 2753 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2745#issuecomment-58771859
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21652/consoleFull)
for PR 2745 at commit
Github user manishamde commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58772394
@mengxr The test failures seem to be due to lack of permission. Could you
please enable it.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58772417
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21653/consoleFull)
for PR 2607 at commit
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2765#discussion_r18745606
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/FileInputDStream.scala
---
@@ -240,6 +260,31 @@ class FileInputDStream[K: ClassTag,
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2765#discussion_r18745609
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/FileInputDStream.scala
---
@@ -240,6 +260,31 @@ class FileInputDStream[K: ClassTag,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58772720
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21654/consoleFull)
for PR 2607 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2745#issuecomment-58772831
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21652/consoleFull)
for PR 2745 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2745#issuecomment-58772832
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/2753#issuecomment-58772867
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21651/consoleFull)**
for PR 2753 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2753#issuecomment-58772869
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/2607#issuecomment-58772868
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21655/consoleFull)
for PR 2607 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58772988
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21653/consoleFull)
for PR 2607 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58773003
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21656/consoleFull)
for PR 2607 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58772989
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/2607#issuecomment-58773142
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21657/consoleFull)
for PR 2607 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58773260
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/2607#issuecomment-58773258
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21654/consoleFull)
for PR 2607 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58773337
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21658/consoleFull)
for PR 2607 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58773406
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/2607#issuecomment-58773562
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/2607#issuecomment-58773560
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21656/consoleFull)
for PR 2607 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58773733
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/2607#issuecomment-58773732
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21657/consoleFull)
for PR 2607 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58773403
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21655/consoleFull)
for PR 2607 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58773981
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/2607#issuecomment-58773977
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21658/consoleFull)
for PR 2607 at commit
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/2736#issuecomment-58774056
Hi, @ravipesala, you don't need create a new PR, you can update you pr
here(use git push to update this branch)
---
If your project is set up for it, you can reply to this
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2538#issuecomment-58774404
Jenkins, 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
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2773#issuecomment-5877
Jenkins, 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2773#issuecomment-58774530
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21659/consoleFull)
for PR 2773 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2538#issuecomment-58774536
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21660/consoleFull)
for PR 2538 at commit
Github user tigerquoll commented on a diff in the pull request:
https://github.com/apache/spark/pull/2516#discussion_r18745897
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -1479,6 +1479,14 @@ private[spark] object Utils extends Logging {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2538#issuecomment-58774569
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/353/consoleFull)
for PR 2538 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2538#issuecomment-58774562
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/352/consoleFull)
for PR 2538 at commit
101 - 193 of 193 matches
Mail list logo
