Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11976#issuecomment-201709760
**[Test build #54253 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54253/consoleFull)**
for PR 11976 at commit
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/11976
[SPARK-14176][SQL]Add DataFrameWriter.trigger to set the stream batch period
## What changes were proposed in this pull request?
Add a processing time trigger to control the batch
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11975#issuecomment-201707869
**[Test build #54252 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54252/consoleFull)**
for PR 11975 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/11975#issuecomment-201707808
cc @rxin
---
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 davies opened a pull request:
https://github.com/apache/spark/pull/11975
[SPARK-14175] [SQL] whole stage codegen interface refactor
## What changes were proposed in this pull request?
1. merge consumeChild into consume()
2. always generate code for input
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11973#issuecomment-201705308
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/11973#issuecomment-201705306
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/11973#issuecomment-201705270
**[Test build #54247 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54247/consoleFull)**
for PR 11973 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11959#issuecomment-201704676
**[Test build #54251 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54251/consoleFull)**
for PR 11959 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11971#issuecomment-201703542
**[Test build #54250 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54250/consoleFull)**
for PR 11971 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11971#issuecomment-201703467
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11971#issuecomment-201703258
> LGTM but I wonder if just overriding Thread.run and making it final
wouldn't be enough (the task to run would have to be passed as a Runnable). It
would simplify the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11824#issuecomment-201702980
**[Test build #54249 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54249/consoleFull)**
for PR 11824 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11824#issuecomment-201702799
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11829#issuecomment-201702668
Test PASSed.
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/11829#issuecomment-201702667
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11829#issuecomment-201702555
**[Test build #54246 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54246/consoleFull)**
for PR 11829 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11974#issuecomment-201701494
**[Test build #54248 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54248/consoleFull)**
for PR 11974 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11974#issuecomment-201701496
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/11974#issuecomment-201701274
**[Test build #54248 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54248/consoleFull)**
for PR 11974 at commit
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/11974
[SPARK-14174][MLLIB] Accelerate KMeans via Mini-Batch EM
## What changes were proposed in this pull request?
add the support of MiniBatch EM into KMeans
## How was this patch
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11796#issuecomment-201699760
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/11796#issuecomment-201699761
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/11796#issuecomment-201699721
**[Test build #54243 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54243/consoleFull)**
for PR 11796 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11941#issuecomment-201699659
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/11941#issuecomment-201699660
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/11941#issuecomment-201699607
**[Test build #54242 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54242/consoleFull)**
for PR 11941 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11824#issuecomment-201699373
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/11824#issuecomment-201699372
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/11824#issuecomment-201699132
**[Test build #54244 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54244/consoleFull)**
for PR 11824 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11959#issuecomment-201698964
Test PASSed.
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/11959#issuecomment-201698961
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11959#issuecomment-201698540
**[Test build #54245 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54245/consoleFull)**
for PR 11959 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11925
---
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/11973#issuecomment-201696073
**[Test build #54247 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54247/consoleFull)**
for PR 11973 at commit
Github user KaiXinXiaoLei closed the pull request at:
https://github.com/apache/spark/pull/11935
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11973#issuecomment-201689444
Test PASSed.
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/11973#issuecomment-201689441
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11973#issuecomment-201688905
**[Test build #54241 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54241/consoleFull)**
for PR 11973 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11805#issuecomment-201676097
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/11805#issuecomment-201676104
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/11805#issuecomment-201675517
**[Test build #54239 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54239/consoleFull)**
for PR 11805 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11973#issuecomment-201668727
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/11973#issuecomment-201668730
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/11973#issuecomment-201668358
**[Test build #54240 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54240/consoleFull)**
for PR 11973 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11829#issuecomment-201663130
**[Test build #54246 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54246/consoleFull)**
for PR 11829 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11959#issuecomment-201659511
**[Test build #54245 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54245/consoleFull)**
for PR 11959 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/11962#issuecomment-201658339
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/11959#discussion_r57506942
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -53,12 +54,19 @@ case class CreateDatabase(
extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11970#issuecomment-201655218
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/11970#issuecomment-201655216
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/11970#issuecomment-201654857
**[Test build #54236 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54236/consoleFull)**
for PR 11970 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11824#issuecomment-201652844
**[Test build #54244 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54244/consoleFull)**
for PR 11824 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11972#issuecomment-201651975
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/11972#issuecomment-201651969
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/11972#issuecomment-201651615
**[Test build #54238 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54238/consoleFull)**
for PR 11972 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11824#issuecomment-201651190
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/11870#issuecomment-201649600
**[Test build #2697 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2697/consoleFull)**
for PR 11870 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11971#issuecomment-201647819
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/11971#issuecomment-201647814
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/11971#issuecomment-201647391
**[Test build #54235 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54235/consoleFull)**
for PR 11971 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11936#discussion_r57506577
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/orc/OrcRelation.scala ---
@@ -117,6 +123,66 @@ private[sql] class DefaultSource extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11962#issuecomment-201642138
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/11962#issuecomment-201642142
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/11962#issuecomment-201641520
**[Test build #54233 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54233/consoleFull)**
for PR 11962 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11796#issuecomment-201634768
**[Test build #54243 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54243/consoleFull)**
for PR 11796 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11941#issuecomment-201634717
**[Test build #54242 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54242/consoleFull)**
for PR 11941 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11960#issuecomment-201633733
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/11960#issuecomment-201633729
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/11960#issuecomment-201633176
**[Test build #54232 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54232/consoleFull)**
for PR 11960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11796#issuecomment-201632998
Test PASSed.
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/11796#issuecomment-201632991
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11796#issuecomment-201631671
**[Test build #54227 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54227/consoleFull)**
for PR 11796 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/11941#issuecomment-201630876
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/11973#issuecomment-201621999
Looks a bit large, open to suggestions (or to even just live with the
current template...). Avoiding the bullet list would help, at the cost of
making the test a little
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/11973#issuecomment-201621244
---
If your project is set up for it, you can reply to
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11967#discussion_r57505626
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameNaFunctions.scala ---
@@ -402,13 +404,7 @@ final class DataFrameNaFunctions private[sql](df:
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11967#issuecomment-201620355
Looks like there is a test failure.
---
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/11973#issuecomment-201620015
**[Test build #54241 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54241/consoleFull)**
for PR 11973 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11925#issuecomment-201619344
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/11962#issuecomment-201619484
Test PASSed.
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/11962#issuecomment-201619479
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/11925#issuecomment-201619350
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11967#issuecomment-201619013
@traviscrawford can you remove the part about this is your first
contribution from the pr description? The pr description will actually become
part of the commit.
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11962#issuecomment-201618929
**[Test build #54231 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54231/consoleFull)**
for PR 11962 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11925#issuecomment-201618700
**[Test build #54230 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54230/consoleFull)**
for PR 11925 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11972#issuecomment-201618575
cc @yhuai
I took a quick look and it looks good -- but I didn't look at the details.
---
If your project is set up for it, you can reply to this email and have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11895
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11942#issuecomment-201618010
Test PASSed.
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/11942#issuecomment-201618009
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/11895#issuecomment-201617689
Thanks - merging in master.
---
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/11942#issuecomment-201617522
**[Test build #54223 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54223/consoleFull)**
for PR 11942 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11805#issuecomment-201617490
Looks pretty good actually. There are some details about naming and on/off
defaults we need to figure out, but that can go in later.
---
If your project is set up for
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/11973#issuecomment-201614723
Argh the rendering looks horrible, I'll have to find a better way...
---
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/11973#issuecomment-201613623
**[Test build #54240 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54240/consoleFull)**
for PR 11973 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/11973#issuecomment-201612561
Github doesn't actually show the modified template, so I'll have to
manually test things locally some other way... (I tested "fake merging"
existing PRs and that's
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/11973
[SPARK-14170] [infra] Simplify the PR template and remove it when merging.
This change modifies the template so that all instructions are together at
the top, which makes it easy to remove the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11925#issuecomment-201611512
**[Test build #2696 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2696/consoleFull)**
for PR 11925 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11569#issuecomment-201607130
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/11569#issuecomment-201607135
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
1 - 100 of 686 matches
Mail list logo
