Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12017#issuecomment-206160605
Is this PR good to go? Or we still need to update it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12017#issuecomment-206160674
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 this featur
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58659279
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala ---
@@ -47,18 +47,38 @@ case class AnalyzeTable(tableName: String) ex
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58659242
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala ---
@@ -68,10 +91,14 @@ case class DropTable(
// Users sho
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58659065
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala ---
@@ -47,18 +48,40 @@ case class AnalyzeTable(tableName: String) ex
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/12116#issuecomment-206152870
@wangmiao1981 might still be good to add a simple test? But yes we should
run this in jenkins if one of the commiters can whitelist.
---
If your project is set up for
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/11989#discussion_r58657961
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/tree/impl/RandomForestSuite.scala ---
@@ -422,6 +422,13 @@ class RandomForestSuite extends SparkFunSuite wi
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12201#issuecomment-206148855
cc @yhuai Sorry, I did not realize this is not allowed in Scala 2.10
---
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/12201#issuecomment-206148998
**[Test build #55096 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55096/consoleFull)**
for PR 12201 at commit
[`4036cdd`](https://gi
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/12201
[SPARK-14396] [Build] [HOT] Fix compilation against Scala 2.10
What changes were proposed in this pull request?
This PR is to fix the compilation errors in Scala 2.10 build, as shown in
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12199#issuecomment-206146082
**[Test build #55095 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55095/consoleFull)**
for PR 12199 at commit
[`0619067`](https://gi
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/12200#discussion_r58657525
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/feature/CountVectorizerSuite.scala ---
@@ -115,6 +115,27 @@ class CountVectorizerSuite extends SparkFunSuit
Github user wangmiao1981 commented on the pull request:
https://github.com/apache/spark/pull/12116#issuecomment-206145891
@jkbradley Can you add me to white list to trigger the integration test?
Thanks!
Miao
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12161#issuecomment-206142648
**[Test build #55094 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55094/consoleFull)**
for PR 12161 at commit
[`e30d40d`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12198#issuecomment-206142565
**[Test build #55093 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55093/consoleFull)**
for PR 12198 at commit
[`6abe10b`](https://gi
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12199#issuecomment-206141117
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
enabl
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12169#issuecomment-206140527
I see the problem.
```
[error]
/home/jenkins/workspace/spark-master-compile-maven-scala-2.10/sql/hive/src/test/scala/org/apache/spark/sql/hive/HiveDDLCo
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12169#issuecomment-206140754
Will fix it using a PR with [HOT]. Sorry for it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12198#issuecomment-206140681
@yhuai
---
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
ena
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-206140188
**[Test build #55092 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55092/consoleFull)**
for PR 12081 at commit
[`8b6f86b`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12200#issuecomment-206140085
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 p
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12191#issuecomment-206140194
**[Test build #55091 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55091/consoleFull)**
for PR 12191 at commit
[`18bff08`](https://gi
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12169#issuecomment-206139977
https://amplab.cs.berkeley.edu/jenkins/job/spark-master-compile-maven-scala-2.10/
?
---
If your project is set up for it, you can reply to this email and have you
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-206139078
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 thi
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12169#issuecomment-206138869
Or I need to do it in my local environment?
---
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 p
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12199#issuecomment-206138706
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12199#issuecomment-206138708
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12199#issuecomment-206138699
**[Test build #55090 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55090/consoleFull)**
for PR 12199 at commit
[`e54bcc6`](https://g
GitHub user wangmiao1981 opened a pull request:
https://github.com/apache/spark/pull/12200
[SPARK-14392][ML]CountVectorizer Estimator should include binary toggle
Param
## What changes were proposed in this pull request?
CountVectorizerModel has a binary toggle param. This
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12061#issuecomment-206138275
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12061#issuecomment-206138272
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12199#issuecomment-206138185
**[Test build #55090 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55090/consoleFull)**
for PR 12199 at commit
[`e54bcc6`](https://gi
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/12199
[SPARK-14426][SQL] Merge PerserUtils and ParseUtils
## What changes were proposed in this pull request?
We have ParserUtils and ParseUtils which are both utility collections for
use during
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12169#issuecomment-206138089
Sure. Could you show me how to find the build log?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12061#issuecomment-206138075
**[Test build #55087 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55087/consoleFull)**
for PR 12061 at commit
[`98744f0`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12198#issuecomment-206137516
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12198#issuecomment-206137519
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12198#issuecomment-206137508
**[Test build #55089 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55089/consoleFull)**
for PR 12198 at commit
[`a3601fb`](https://g
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12169#issuecomment-206137008
@gatorsmile Seems scala 2.10 build is broken. Can you take a look?
---
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/12198#issuecomment-206136870
**[Test build #55089 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55089/consoleFull)**
for PR 12198 at commit
[`a3601fb`](https://gi
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12183#issuecomment-206136314
@rekhajoshm I've opened #12198 to illustrate what I mean. I don't think the
changes in this patch are correct so I would recommend that we close this PR.
---
If you
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/12198
[SPARK-14410][SQL] Push functions existence check into catalog
## What changes were proposed in this pull request?
This is a followup to #12117 and addresses some of the TODOs introduced
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
[`cb050a0`](https://gi
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 script
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 ena
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 hav
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 en
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 thi
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 ena
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 ena
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 thi
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):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
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 projec
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
[`2d7cee8`](https://g
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 ena
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 proj
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
[`98744f0`](https://gi
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
[`ae3998d`](https://gi
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
e
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 (and
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 projec
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):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
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):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
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
[`c96ceae`](https://g
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 projec
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
[`a793696`](https://g
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 SparkSqlAst
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 appe
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
ena
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 ena
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 thi
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):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
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 projec
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
[`3c03dbf`](https://g
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 projec
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):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
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
[`8b1cdaa`](https://g
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 projec
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):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
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
[`33abf5c`](https://g
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
[`c96ceae`](https://gi
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 ena
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):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
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 projec
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
[`af0d193`](https://g
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
[`2d7cee8`](https://gi
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):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
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 projec
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
[`8b6f86b`](https://g
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 well
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 projec
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):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
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
[`c6fbf0f`](https://g
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 projec
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):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
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
[`0ce90fe`](https://g
1 - 100 of 925 matches
Mail list logo
