Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8207#issuecomment-132331967
LGTM. Merged into master and branch-1.5. 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
Github user feynmanliang commented on the pull request:
https://github.com/apache/spark/pull/8197#issuecomment-132333581
Having a `ml-summary.md` would lead to quite a bit of repeated
documentation; we would have to supply model training example code in both the
model's description
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8271#discussion_r37347311
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Matrices.scala
---
@@ -281,9 +281,13 @@ class DenseMatrix(
/**
* @since
Github user feynmanliang commented on the pull request:
https://github.com/apache/spark/pull/8271#issuecomment-132336480
minor suggestion but LGTM
CC @mengxr @jkbradley for final pass
---
If your project is set up for it, you can reply to this email and have your
reply
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/8197#issuecomment-132341432
You are right.
But I thought that the example code such as extracting the training loss,
and common metrics would be repeated across some classification and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8285#issuecomment-132341614
[Test build #41160 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41160/consoleFull)
for PR 8285 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8197#issuecomment-132343547
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8285#issuecomment-132343518
Merged build triggered.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8069
---
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/8285#issuecomment-132343525
Merged build started.
---
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/8182#issuecomment-132354472
No particular reason. Just want to have less hash collision while keeping
the computation cheap. 16 is certainly not sufficient. See
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8007#discussion_r37354752
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/YarnSchedulerBackend.scala
---
@@ -91,6 +92,68 @@ private[spark] abstract class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8257#issuecomment-132356303
[Test build #1652 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1652/consoleFull)
for PR 8257 at commit
Github user sabhyankar commented on the pull request:
https://github.com/apache/spark/pull/8241#issuecomment-132364417
@holdenk yep :) I am updating those as well!
---
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 mccheah commented on a diff in the pull request:
https://github.com/apache/spark/pull/8007#discussion_r37358117
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/YarnSchedulerBackend.scala
---
@@ -91,6 +92,66 @@ private[spark] abstract class
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/7380#issuecomment-132368741
Okay, I merged this into master and branch-1.5 so we can unblock
SPARK-9864. @MechCoder Please fix the issue you found in your PR. Thanks
@BryanCutler for adding
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8256#issuecomment-132371898
@XiaoqingWang I submitted #8288 based on your work, because we want to get
this merged soon to unblock SPARK-9864. Thanks for your contribution!
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8033#issuecomment-132374577
[Test build #1650 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1650/console)
for PR 8033 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8223
---
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/8033#issuecomment-132331525
[Test build #1650 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1650/consoleFull)
for PR 8033 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8225
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/8227#issuecomment-132332636
Merged into master and branch-1.5. 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
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8267#discussion_r37346365
--- Diff: docs/ml-features.md ---
@@ -1389,3 +1389,145 @@ print(output.select(features, clicked).first())
# Feature Selectors
+##
Github user feynmanliang commented on the pull request:
https://github.com/apache/spark/pull/8267#issuecomment-132333980
Could you also modify the title to include java tests and python API?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8271#issuecomment-132339964
Merged build started.
---
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 feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8197#discussion_r37349237
--- Diff: docs/ml-linear-methods.md ---
@@ -118,12 +133,114 @@ lrModel = lr.fit(training)
print(Weights: + str(lrModel.weights))
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8285#issuecomment-132342162
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/8285#issuecomment-132342151
[Test build #41160 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41160/console)
for PR 8285 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8285#issuecomment-132342156
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/8257#issuecomment-132342208
[Test build #1651 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1651/consoleFull)
for PR 8257 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-132345408
welcome back @shaneknapp !
---
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/8197#issuecomment-132348051
[Test build #41162 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41162/console)
for PR 8197 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8184#issuecomment-132350411
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 MechCoder commented on the pull request:
https://github.com/apache/spark/pull/8197#issuecomment-132350267
Okay. But he had to told something else in that PR discussion :p. I do
agree that doing model.binarySUmmary is much nearer than
model.asInstanceOf[]â¦
On
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8184#issuecomment-132350174
[Test build #41163 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41163/console)
for PR 8184 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8007#discussion_r37356067
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -207,6 +211,17 @@ private[yarn] class YarnAllocator(
}
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/8242#discussion_r37357797
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
---
@@ -439,6 +465,30 @@ class ReceiverTracker(ssc:
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8244#discussion_r37357835
--- Diff: docs/ml-decision-tree.md ---
@@ -0,0 +1,506 @@
+---
+layout: global
+title: Decision Trees - SparkML
+displayTitle: a
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8244#discussion_r37357841
--- Diff: docs/ml-decision-tree.md ---
@@ -0,0 +1,506 @@
+---
+layout: global
+title: Decision Trees - SparkML
+displayTitle: a
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8223#issuecomment-132365457
@jkbradley do we need to wait for something here? things can go into
`master` safely; this looks safe for `branch-1.5` too regardless of whether it
makes this RC or
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8282
---
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/8241#issuecomment-132365264
Great :)
---
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8007#discussion_r37359214
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -207,6 +211,17 @@ private[yarn] class YarnAllocator(
}
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7380
---
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/8218#issuecomment-132369642
[Test build #41156 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41156/console)
for PR 8218 at commit
Github user mccheah commented on a diff in the pull request:
https://github.com/apache/spark/pull/8007#discussion_r37359578
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -207,6 +211,17 @@ private[yarn] class YarnAllocator(
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8218#issuecomment-132369817
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/8288#issuecomment-132371705
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8287#issuecomment-132371678
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8287#issuecomment-132371704
Merged build started.
---
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/8287#issuecomment-132372715
[Test build #41165 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41165/consoleFull)
for PR 8287 at commit
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/8244#discussion_r37362286
--- Diff: docs/ml-decision-tree.md ---
@@ -0,0 +1,506 @@
+---
+layout: global
+title: Decision Trees - SparkML
+displayTitle: a
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8280#issuecomment-132415909
Ok - lets leave it on in master and I'll work with @mateiz on changes to
move this to ShuffleRDD and capture more use cases. @yhuai could you put in the
query you ran
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8294#issuecomment-132418073
[Test build #41196 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41196/consoleFull)
for PR 8294 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8297
---
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/8297#issuecomment-132417968
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-132418585
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 not
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/8294#issuecomment-132418520
LGTM. Will merge when tests pass.
---
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 hvanhovell opened a pull request:
https://github.com/apache/spark/pull/8298
[SPARK-10100] [SQL] Perfomance improvements to new MIN/MAX aggregate
functions.
The new MIN/MAX suffer from a performance regression. This PR aims to fix
this by simplifying the evaluation of
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8266#issuecomment-132426562
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8168#issuecomment-132427026
[Test build #1660 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1660/console)
for PR 8168 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8275#issuecomment-132428215
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/8275#issuecomment-132428214
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 tdas opened a pull request:
https://github.com/apache/spark/pull/8299
[SPARK-9967][SPARK-10099][STREAMING] Small changes
Small changes
- Renamed conf spark.streaming.backpressure.{enable -- enabled}
- Change Java Deprecated annotations to Scala deprecated
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8266#issuecomment-132429295
[Test build #41198 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41198/console)
for PR 8266 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/8299#discussion_r37376281
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/RateController.scala
---
@@ -76,9 +76,9 @@ private[streaming] abstract class
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8168#issuecomment-132430944
All builds in the last build wave passed (the last one timed out, but test
suites we care about passed). I'm merging this into master and branch-1.5.
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-132431832
[Test build #41202 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41202/consoleFull)
for PR 8026 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8168
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/8266#issuecomment-132431814
LGTM. Merging this. @yu-iskw Can you open a JIRA for the `if-else` issue ?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8266
---
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/8298#issuecomment-132437613
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8298#issuecomment-132437659
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8298#issuecomment-132437669
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8275#issuecomment-132437660
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8275#issuecomment-132437698
Merged build started.
---
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/8298#issuecomment-132437956
[Test build #41203 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41203/consoleFull)
for PR 8298 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8295#issuecomment-132439632
[Test build #41192 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41192/console)
for PR 8295 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7150#issuecomment-132440101
[Test build #41206 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41206/consoleFull)
for PR 7150 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8294#issuecomment-132442233
**[Test build #41191 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41191/console)**
for PR 8294 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8294#issuecomment-132442351
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/8294#issuecomment-132442354
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/8026#issuecomment-13249
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-132445384
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/8026#issuecomment-132445382
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/8026#issuecomment-132445340
[Test build #41211 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41211/consoleFull)
for PR 8026 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-132445375
[Test build #41211 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41211/console)
for PR 8026 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/8294#discussion_r37373582
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
---
@@ -469,7 +469,7 @@ class ReceiverTracker(ssc:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132415613
[Test build #41195 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41195/consoleFull)
for PR 8297 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8168#issuecomment-132415769
[Test build #1659 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1659/console)
for PR 8168 at commit
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/8266#discussion_r37374083
--- Diff: R/pkg/R/functions.R ---
@@ -163,3 +163,17 @@ setMethod(n, signature(x = Column),
function(x) {
count(x)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-132416914
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/7629#issuecomment-132416671
[Test build #41174 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41174/console)
for PR 7629 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-132416917
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132418318
@shivaram thank you for reviewing and merging 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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/8276#issuecomment-132418166
@sun-rui We can do the `createDataFrame` in another PR, but for this PR can
we add a test case using a JSON file which has an `ArrayType` in it ?
---
If your project
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8218#issuecomment-132418179
Let's try pinging a couple of people. @rxin @aarondav
---
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 davies opened a pull request:
https://github.com/apache/spark/pull/8300
[SPARK-10073] [SQL] Python withColumn should replace the old column
DataFrame.withColumn in Python should be consistent with the Scala one
(replacing the existing column that has the same name).
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8300#issuecomment-132439153
Merged build triggered.
---
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 yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8266#issuecomment-132440315
Sure. Thank you for merging 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 your project does not
501 - 600 of 1166 matches
Mail list logo
