Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12197#issuecomment-206129528
**[Test build #55088 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55088/consoleFull)**
for PR 12197 at commit
GitHub user holdenk opened a pull request:
https://github.com/apache/spark/pull/12197
[SPARK-14424][BUILD][DOCS] Update the build docs to switch from assembly to
package and add a noâ¦
## What changes were proposed in this pull request?
Change our build docs & shell
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12193
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12193#issuecomment-206127119
LGTM merged into 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
Github user holdenk closed the pull request at:
https://github.com/apache/spark/pull/12196
---
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/12196#issuecomment-206126910
Or wait looks like just updating the build docs is the right path forward.
I'll close and re-open a DOC fix.
---
If your project is set up for it, you can reply to
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12169
---
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/12188
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12169#issuecomment-206126467
Merged into 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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12188#issuecomment-206126096
Mergd into amster
---
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/12185#issuecomment-206126348
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/12185#issuecomment-206126343
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/12185#issuecomment-206125926
**[Test build #55084 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55084/consoleFull)**
for PR 12185 at commit
Github user lw-lin closed the pull request at:
https://github.com/apache/spark/pull/12035
---
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 lw-lin commented on the pull request:
https://github.com/apache/spark/pull/12035#issuecomment-206123094
@srowen sure, thank you for this review, :-)
---
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 pravingadakh commented on the pull request:
https://github.com/apache/spark/pull/12176#issuecomment-206119313
@jkbradley Could you please flag this PR for test build?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12061#issuecomment-206118365
**[Test build #55087 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55087/consoleFull)**
for PR 12061 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12196#issuecomment-206117843
**[Test build #55086 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55086/consoleFull)**
for PR 12196 at commit
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/12196#issuecomment-206117606
cc @vanzin
---
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 holdenk opened a pull request:
https://github.com/apache/spark/pull/12196
[SPARK-14424][BUILD] Revert "Stop building the main Spark assembly." â¦
## What changes were proposed in this pull request?
This reverts SPARK-13579 to temporarily restore spark-class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11419#issuecomment-206116388
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/11419#issuecomment-206116392
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/12083#issuecomment-206116277
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/12083#issuecomment-206116274
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/11419#issuecomment-206116242
**[Test build #55085 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55085/consoleFull)**
for PR 11419 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12083#issuecomment-206116130
**[Test build #55082 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55082/consoleFull)**
for PR 12083 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58649986
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/HiveSqlParser.scala
---
@@ -113,7 +113,10 @@ class HiveSqlAstBuilder extends
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206114097
Seems this PR does not change unpersist? Is the behavior of unpersist
correct?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12190#issuecomment-206113594
wrong jira?
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/12186
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/12186#issuecomment-206113198
LGTM. Merging to 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-206113036
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/12081#issuecomment-206113034
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/12081#issuecomment-206112938
**[Test build #55077 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55077/consoleFull)**
for PR 12081 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12193#issuecomment-206112823
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/12193#issuecomment-206112826
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/12193#issuecomment-206111910
**[Test build #55073 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55073/consoleFull)**
for PR 12193 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12188#issuecomment-206111716
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/12188#issuecomment-206111717
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/12188#issuecomment-206111568
**[Test build #55070 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55070/consoleFull)**
for PR 12188 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11419#issuecomment-206110770
**[Test build #55085 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55085/consoleFull)**
for PR 11419 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12087
---
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/12087#issuecomment-206110555
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12087#issuecomment-206110534
merging to 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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12087#issuecomment-206110552
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/12087#issuecomment-206110316
**[Test build #55079 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55079/consoleFull)**
for PR 12087 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12185#issuecomment-206110211
**[Test build #55084 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55084/consoleFull)**
for PR 12185 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-206110043
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/12081#issuecomment-206110041
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/12081#issuecomment-206109929
**[Test build #55078 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55078/consoleFull)**
for PR 12081 at commit
Github user zhengruifeng commented on the pull request:
https://github.com/apache/spark/pull/12135#issuecomment-206109616
@holdenk Ok, I will add the python API into this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12191#issuecomment-206108421
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/12191#issuecomment-206108422
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/12191#issuecomment-206108305
**[Test build #55080 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55080/consoleFull)**
for PR 12191 at commit
Github user lw-lin commented on the pull request:
https://github.com/apache/spark/pull/12174#issuecomment-206107803
@srowen thanks for the fix.
However, instead of allowing users to call these obsolete constructors and
improving the error messages, I'm inclined to guide users
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12087#issuecomment-206107326
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/12087#issuecomment-206107327
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/12087#issuecomment-206107113
**[Test build #55076 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55076/consoleFull)**
for PR 12087 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12195#issuecomment-206107020
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/12195#issuecomment-206106967
**[Test build #55083 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55083/consoleFull)**
for PR 12195 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12195#issuecomment-206107019
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/12087#issuecomment-206104505
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/12087#issuecomment-206104497
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/12087#issuecomment-206103496
**[Test build #55075 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55075/consoleFull)**
for PR 12087 at commit
Github user keypointt commented on the pull request:
https://github.com/apache/spark/pull/12195#issuecomment-206102900
Unsure code duplications (need doube check)
- AbstractParams.scala - cannot delete this one, not duplicate, its usage
found in many examples
-
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12195#issuecomment-206101554
**[Test build #55083 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55083/consoleFull)**
for PR 12195 at commit
GitHub user keypointt opened a pull request:
https://github.com/apache/spark/pull/12195
[Spark-14300][Docs][MLLIB]Scala MLlib examples code merge and clean up
## What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/SPARK-14300
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12169#issuecomment-206100034
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/12169#issuecomment-206100033
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/12169#issuecomment-206099910
**[Test build #55072 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55072/consoleFull)**
for PR 12169 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/12171#issuecomment-206099245
Hmm, the FlumePollingStreamSuite test looks broken because it has hung
twice now. I'll try to reproduce offline.
---
If your project is set up for it, you can reply
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206098980
Hi, @jaceklaskowski and @marmbrus .
Thank you for fixing this. I didn't notice there is such a problem.
Sorry for late response!
I have another PR
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12106#issuecomment-206098700
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/12106#issuecomment-206098699
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/12194#issuecomment-206098651
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12106#issuecomment-206098633
**[Test build #55081 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55081/consoleFull)**
for PR 12106 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12194#issuecomment-206097196
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/12194#issuecomment-206097201
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/12194#issuecomment-206097091
**[Test build #55074 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55074/consoleFull)**
for PR 12194 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12035#issuecomment-206096337
@lw-lin you can close this PR given
https://github.com/apache/spark/pull/12174
---
If your project is set up for it, you can reply to this email and have your
reply
Github user liyezhang556520 commented on the pull request:
https://github.com/apache/spark/pull/12083#issuecomment-206096350
@vanzin , @zsxwing , I have changed the buffer limit to 256K. I do agree
that it's better we handle this issue by manually copying data to directBuffer,
so no
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12087#discussion_r58646052
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DatasetBenchmark.scala ---
@@ -0,0 +1,85 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206095830
@tdas another streaming 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9524#issuecomment-206095658
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206095697
Is this really the patch to cause the issue or is this more an interim
hiccup?
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9524#issuecomment-206095656
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/9524#issuecomment-206095475
**[Test build #55067 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55067/consoleFull)**
for PR 9524 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206095409
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/12192#issuecomment-206095407
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/12192#issuecomment-206095328
**[Test build #55069 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55069/consoleFull)**
for PR 12192 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/12087#discussion_r58645473
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DatasetBenchmark.scala ---
@@ -0,0 +1,85 @@
+/*
+ * Licensed to the Apache Software
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12174
---
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 hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/12106#discussion_r58645358
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/LDAOptimizer.scala ---
@@ -451,10 +451,10 @@ final class OnlineLDAOptimizer extends
Github user hhbyyh commented on the pull request:
https://github.com/apache/spark/pull/12106#issuecomment-206094396
@jkbradley Updated. I used flatMap to replace the second reduce.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12083#issuecomment-206094443
**[Test build #55082 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55082/consoleFull)**
for PR 12083 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/12174#issuecomment-206094362
Thanks, merging to 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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12087#discussion_r58645093
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DatasetBenchmark.scala ---
@@ -0,0 +1,85 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11105#issuecomment-206090552
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/11105#issuecomment-206090548
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/11105#issuecomment-206089849
**[Test build #55064 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55064/consoleFull)**
for PR 11105 at commit
1 - 100 of 916 matches
Mail list logo
