Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11014
---
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 marmbrus closed the pull request at:
https://github.com/apache/spark/pull/11011
---
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 sourind closed the pull request at:
https://github.com/apache/spark/pull/10907
---
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/10953#issuecomment-178746978
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/11020#issuecomment-178749394
Thanks - going to merge this.
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/10601#issuecomment-178756172
@vijaykiran Could you fix the doc build warnings in `tree.py`? I saw the
following by running `make clean html` under `python/docs`:
~~~
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11007#issuecomment-178756109
**[Test build #50571 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50571/consoleFull)**
for PR 11007 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10953#issuecomment-178756201
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10141#issuecomment-178769507
ok to test
---
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/10141#issuecomment-178779419
**[Test build #50580 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50580/consoleFull)**
for PR 10141 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10930#issuecomment-178779356
**[Test build #50579 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50579/consoleFull)**
for PR 10930 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11028#issuecomment-178781605
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/10702#issuecomment-178781745
**[Test build #50575 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50575/consoleFull)**
for PR 10702 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/10953#issuecomment-178786575
You already are on it, given the tests for you PR started automatically
when you submitted it.
---
If your project is set up for it, you can reply to this email and
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/10702#issuecomment-178787032
I meat comparing the result with your solution when `yStd != 0`, and
`regParm != 0`. I suspect that you will get different result since GLMNET one
forces to standardize
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11028#issuecomment-178793423
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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11022#issuecomment-178793779
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/10953#issuecomment-178803662
**[Test build #50588 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50588/consoleFull)**
for PR 10953 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10941#issuecomment-178731963
Can you close this PR? (PRs not against master don't auto close)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10741#issuecomment-178731705
ok to test
---
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/10741#issuecomment-178732985
**[Test build #50573 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50573/consoleFull)**
for PR 10741 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10960#issuecomment-178754162
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/10960#issuecomment-178754165
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/10610#issuecomment-178754288
LGTM. Merged into master. 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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11007#issuecomment-178759342
@gabrielenizzoli I have merged this PR to branch 1.6. Could you open a new
PR to fix the master branch and close this one? Thanks!
---
If your project is set up for
Github user markgrover commented on the pull request:
https://github.com/apache/spark/pull/10953#issuecomment-178763362
Jenkins, 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
Github user markgrover commented on the pull request:
https://github.com/apache/spark/pull/10953#issuecomment-178763349
The previous test failures seems like a timeout when fetching the PR from
github:
```
> git fetch --tags --progress https://github.com/apache/spark.git
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11007#issuecomment-178776404
> @zsxwing yes, I will close this PR and create a new one for master.
Should I assign the same jira issue number to the PR for master?
Just make the new PR has
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10943#issuecomment-178776399
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/10702#issuecomment-178782152
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user markgrover commented on the pull request:
https://github.com/apache/spark/pull/10953#issuecomment-178784728
Can someone add me to the whitelist please? Thanks!
---
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 zhuoliu opened a pull request:
https://github.com/apache/spark/pull/11029
[SPARK-13126] fix the right margin of history page.
The right margin of the history page is little bit off. A simple fix for
that issue.
You can merge this pull request into a Git repository by
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11012#issuecomment-178793683
Quoting from the JIRA ticket:
> In our particular case, this behavior manifests since the
currentTaskAttemptId() method is returning -1 for each Spark
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10943#discussion_r51608477
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/DataFrame.scala ---
@@ -1255,9 +1240,9 @@ class DataFrame private[sql](
*/
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/11006#issuecomment-178730617
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
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/10943#discussion_r51609364
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/DataFrame.scala ---
@@ -150,6 +153,14 @@ class DataFrame private[sql](
}
}
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/10943#discussion_r51612126
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/DataFrame.scala ---
@@ -1255,9 +1240,9 @@ class DataFrame private[sql](
*/
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10964
---
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 BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/10601#discussion_r51619200
--- Diff: python/pyspark/mllib/tree.py ---
@@ -305,31 +326,39 @@ def trainClassifier(cls, data, numClasses,
categoricalFeaturesInfo, numTrees,
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10741
---
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/11022#issuecomment-178775586
**[Test build #50581 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50581/consoleFull)**
for PR 11022 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10852#issuecomment-178776116
oh, didn't notice it. Will update it soon
---
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/11021#issuecomment-178776051
Thanks - merging this in.
---
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 gabrielenizzoli opened a pull request:
https://github.com/apache/spark/pull/11028
[SPARK-13121] [Streaming] java mapWithState mishandles scala Optionjava
mapwithstate broken java mapping
Already merged into 1.6 branch, this PR is to commit to master the same
change
Github user markgrover commented on the pull request:
https://github.com/apache/spark/pull/10953#issuecomment-178797235
Jenkins, 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
Github user markgrover commented on the pull request:
https://github.com/apache/spark/pull/10953#issuecomment-178797109
Ok, thanks, Marcelo. I didn't think I was because Jenkins didn't trigger on
my explicit request but I will try again.
---
If your project is set up for it, you can
Github user ajbozarth commented on the pull request:
https://github.com/apache/spark/pull/11029#issuecomment-178800563
Can you post a screenshot?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11022#issuecomment-178800736
**[Test build #50586 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50586/consoleFull)**
for PR 11022 at commit
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/11012#discussion_r51628572
--- Diff: core/src/main/scala/org/apache/spark/storage/MemoryStore.scala ---
@@ -304,10 +309,9 @@ private[spark] class MemoryStore(blockManager:
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11006
---
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 jkbradley closed the pull request at:
https://github.com/apache/spark/pull/10950
---
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 kevinyu98 reopened a pull request:
https://github.com/apache/spark/pull/11009
[SPARK-12987][SQL]Fixing the name resolution in drop column
@marmbrus @cloud-fan @thomas @jayadevan : Hello All: Can you help review
this code fix?
This problem is coming from drop
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11020
---
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/10960#issuecomment-178753559
**[Test build #50569 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50569/consoleFull)**
for PR 10960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11007#issuecomment-178756517
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/11007#issuecomment-178756522
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/10598#issuecomment-178756465
@vijaykiran Could you fix the doc warnings in `classification.py`? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10741#issuecomment-178760390
**[Test build #50573 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50573/consoleFull)**
for PR 10741 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10741#issuecomment-178760924
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10930#issuecomment-178769268
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 iyounus commented on the pull request:
https://github.com/apache/spark/pull/10702#issuecomment-178770437
GLMNET sets all coefficients to zero if yStd=0 and fitIntercept=false
regardless of standardization or regularization. Thats why I cannot compare my
normal equation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10953#issuecomment-178775094
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/10953#issuecomment-178775083
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 dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/10943#issuecomment-178775551
@cloud-fan Can we retest 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10960
---
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/10989#issuecomment-178800319
**[Test build #50587 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50587/consoleFull)**
for PR 10989 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11028#issuecomment-178800234
**[Test build #50585 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50585/consoleFull)**
for PR 11028 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11007#issuecomment-178757483
Merging to master and 1.6. Thanks @gabrielenizzoli
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10741#issuecomment-178760925
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/11019#issuecomment-178765458
**[Test build #50570 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50570/consoleFull)**
for PR 11019 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10852#issuecomment-178769783
I'm sorry... I let this go stale.
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11012#issuecomment-178785689
> An alternative option might be to track unroll/pending unroll memory
based on block ID rather than task attempt ID.
I think you need to account for this on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10960#issuecomment-178801022
**[Test build #50572 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50572/consoleFull)**
for PR 10960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10953#issuecomment-178746983
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/10960#issuecomment-178752121
LGTM pending Jenkins. It is great to see 5x speedup!
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/10580#issuecomment-178755682
@sun-rui @felixcheung I'm going to backport this to branch-1.6 so that the
bug fix is available in 1.6.1. Let me know if you think there is a problem with
it
---
If
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/10960#issuecomment-178758941
Merging this into master, 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10943#issuecomment-178767857
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/10943#issuecomment-178767852
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11022#issuecomment-178772621
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11022#issuecomment-178773138
@mariobriggs could you post a screenshot? 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
Github user gabrielenizzoli closed the pull request at:
https://github.com/apache/spark/pull/11007
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10943#issuecomment-178783451
**[Test build #50582 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50582/consoleFull)**
for PR 10943 at commit
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/10943#discussion_r51611035
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/DataFrame.scala ---
@@ -1220,19 +1213,11 @@ class DataFrame private[sql](
* @since 1.3.0
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/10950#issuecomment-178738438
Closing manually
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-178744134
```
[joshrosen@amp-jenkins-worker-05 ~]$ sudo docker pull
lresende/db2express-c:10.5.0.5-3.10.0
Pulling repository lresende/db2express-c
FATA[0001] Could
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/10741#issuecomment-178740062
LGTM pending tests
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10610
---
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 iyounus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10702#discussion_r51615248
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -398,7 +422,8 @@ class LinearRegressionModel private[ml] (
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10953#issuecomment-178756198
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/11019#issuecomment-178765823
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/11019#issuecomment-178765827
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/11012#issuecomment-178782148
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10702#issuecomment-178782146
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/11012#issuecomment-178782116
/cc @JoshRosen
---
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/11012#issuecomment-178790263
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/11012#issuecomment-178790259
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 davies commented on the pull request:
https://github.com/apache/spark/pull/10989#issuecomment-178795082
```
val dim = broadcast(sqlContext.range(1 << 16).selectExpr("id as k",
"cast(id as string) as v"))
sqlContext.range(values).join(dim, (col("id") % 6) ===
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10960#issuecomment-178801436
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/10960#issuecomment-178801443
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
1 - 100 of 835 matches
Mail list logo
