Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2206#issuecomment-53929667
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19492/consoleFull)
for PR 2206 at commit
[`254248a`](https://github.com/ap
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/2187#issuecomment-53929877
Writers are not thread safe, so that is fine.
Updating reportedPosition might be sufficient; a naive analysis did suggest
that was minimal change required to this p
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/2206#discussion_r16921129
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -174,7 +174,7 @@ private[spark] class ApplicationMaster(ar
GitHub user dbtsai opened a pull request:
https://github.com/apache/spark/pull/2207
[SPARK-3317][MLlib] The loss of regularization in Updater should use the
oldWeights
The current loss of the regularization is computed from the newWeights
which is not correct. The loss, R(w) = 1/2
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2207#issuecomment-53932470
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19493/consoleFull)
for PR 2207 at commit
[`1447c23`](https://github.com/ap
GitHub user dbtsai reopened a pull request:
https://github.com/apache/spark/pull/2207
[SPARK-3317][MLlib] The loss of regularization in Updater should use the
oldWeights
The current loss of the regularization is computed from the newWeights
which is not correct. The loss, R(w) = 1/
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/2207#issuecomment-53933078
LBFGS needs correct loss to find next weights while SGD doesn't.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user dbtsai closed the pull request at:
https://github.com/apache/spark/pull/2207
---
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 enab
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2203#issuecomment-53933306
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
ena
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2195#issuecomment-5399
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
ena
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2195#issuecomment-53933351
/cc @liancheng
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2189#issuecomment-53933376
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
ena
Github user rxin closed the pull request at:
https://github.com/apache/spark/pull/1152
---
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 enable
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2203#issuecomment-53933865
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19496/consoleFull)
for PR 2203 at commit
[`b671f67`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2195#issuecomment-53933873
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19495/consoleFull)
for PR 2195 at commit
[`792f009`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2205#issuecomment-53933841
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19494/consoleFull)
for PR 2205 at commit
[`7e3016a`](https://github.com/ap
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/2205#discussion_r16922689
--- Diff: python/pyspark/__init__.py ---
@@ -61,13 +61,16 @@
from pyspark.conf import SparkConf
from pyspark.context import SparkContext
-fr
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2195#issuecomment-53934204
Good catch, 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 fea
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2205#discussion_r16922982
--- Diff: python/pyspark/__init__.py ---
@@ -61,13 +61,16 @@
from pyspark.conf import SparkConf
from pyspark.context import SparkContext
-fr
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2206#issuecomment-53934987
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19492/consoleFull)
for PR 2206 at commit
[`254248a`](https://github.com/a
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2142#issuecomment-53935085
To check my understanding of the error-correction code:
- Due to hash collisions, we may underestimate the true number of distinct
items.
- Given a set of `
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2205#discussion_r16923130
--- Diff: python/pyspark/__init__.py ---
@@ -61,13 +61,16 @@
from pyspark.conf import SparkConf
from pyspark.context import SparkContext
Github user erikerlandson commented on the pull request:
https://github.com/apache/spark/pull/1964#issuecomment-53936014
@yu-iskw, your use case above with `setMeasure` is definitely how I
envisioned it working, in terms of passing in metric functions as parameters.
I'm some
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/2208
[SPARK-3234][Build] Fixed environment variables that rely on deprecated
command line options in make-distribution.sh
Please refer to
[SPARK-3234](https://issues.apache.org/jira/browse/SPARK-3234)
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/2209
[SPARK-2890][SQL] Allow reading of data when case insensitive resolution
could cause possible ambiguity.
You can merge this pull request into a Git repository by running:
$ git pull https://
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2208#discussion_r16923563
--- Diff: make-distribution.sh ---
@@ -175,7 +185,7 @@ cp "$FWDIR"/examples/target/scala*/spark-examples*.jar
"$DISTDIR/lib/"
mkdir -p "$DISTDIR/example
Github user xinyunh commented on a diff in the pull request:
https://github.com/apache/spark/pull/2099#discussion_r16923632
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/numericOperations.scala
---
@@ -0,0 +1,78 @@
+package org.apache.spark.sq
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-53936431
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19498/consoleFull)
for PR 2209 at commit
[`a703ff4`](https://github.com/ap
Github user xinyunh commented on a diff in the pull request:
https://github.com/apache/spark/pull/2099#discussion_r16923701
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregates.scala
---
@@ -409,3 +424,15 @@ case class FirstFunction(expr: Expr
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2208#issuecomment-53936464
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19499/consoleFull)
for PR 2208 at commit
[`fb26de8`](https://github.com/ap
Github user xinyunh commented on a diff in the pull request:
https://github.com/apache/spark/pull/2099#discussion_r16923711
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -323,6 +328,10 @@ class SqlParser extends StandardTokenParsers with
Github user xinyunh commented on a diff in the pull request:
https://github.com/apache/spark/pull/2099#discussion_r16923732
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/numericOperations.scala
---
@@ -0,0 +1,78 @@
+package org.apache.spark.sq
Github user xinyunh commented on a diff in the pull request:
https://github.com/apache/spark/pull/2099#discussion_r16923739
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/numericOperations.scala
---
@@ -0,0 +1,78 @@
+package org.apache.spark.sq
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2201#issuecomment-53936750
Thanks Nick! This is merged.
---
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 ha
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2201
---
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 enab
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2208#discussion_r16923894
--- Diff: make-distribution.sh ---
@@ -175,7 +185,7 @@ cp "$FWDIR"/examples/target/scala*/spark-examples*.jar
"$DISTDIR/lib/"
mkdir -p "$DISTDIR/exampl
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/2099#discussion_r16923882
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/numericOperations.scala
---
@@ -0,0 +1,78 @@
+package org.apache.spark.s
GitHub user holdenk opened a pull request:
https://github.com/apache/spark/pull/2210
Documentation update in addFile on how to use SparkFiles.get
Rather than specifying the path to SparkFiles we need to use the filename.
You can merge this pull request into a Git repository by runni
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1750
---
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 enab
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1750#issuecomment-53937028
Thanks @willb. I've merged this to master. We'll back port it to branch
1.1 after the release.
---
If your project is set up for it, you can reply to this email and h
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2205#discussion_r16923970
--- Diff: python/pyspark/__init__.py ---
@@ -61,13 +61,16 @@
from pyspark.conf import SparkConf
from pyspark.context import SparkContext
-fr
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/2208#discussion_r16923967
--- Diff: make-distribution.sh ---
@@ -175,7 +185,7 @@ cp "$FWDIR"/examples/target/scala*/spark-examples*.jar
"$DISTDIR/lib/"
mkdir -p "$DISTDIR/example
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2207#issuecomment-53937177
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19493/consoleFull)
for PR 2207 at commit
[`1447c23`](https://github.com/a
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2208
---
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 enab
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2155#issuecomment-53937341
Thanks! I've merged this 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
Github user benoyantony commented on a diff in the pull request:
https://github.com/apache/spark/pull/2206#discussion_r16924081
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -174,7 +174,7 @@ private[spark] class ApplicationMaster(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2205#issuecomment-53937444
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19502/consoleFull)
for PR 2205 at commit
[`f7b35be`](https://github.com/ap
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2190#issuecomment-53937522
Thanks! I've merged this 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2155
---
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 enab
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/2211
[SPARK-1919] Fix Windows spark-shell --jars
We were trying to add `file:/C:/path/to/my.jar` to the class path. We
should add `C:/path/to/my.jar` instead (see changes in `SparkILoop.scala`. The
c
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2171#issuecomment-53937603
Thanks! I've merged this into master and 1.1.
---
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 pr
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2190
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2171
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2191
---
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 enab
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2084#issuecomment-53937805
Thanks! I've merged this 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 doe
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2084
---
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 enab
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2205#issuecomment-53938109
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19494/consoleFull)
for PR 2205 at commit
[`7e3016a`](https://github.com/a
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2207#issuecomment-53938249
@dbtsai The scaladoc for `Updater` says the return value is:
```
A tuple of 2 elements. The first element is a column matrix containing
updated weights,
an
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2206#discussion_r16924446
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -174,7 +174,7 @@ private[spark] class ApplicationMaster(args:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2144#issuecomment-53938391
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19504/consoleFull)
for PR 2144 at commit
[`42fb5fa`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2195#issuecomment-53939282
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19495/consoleFull)
for PR 2195 at commit
[`792f009`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2203#issuecomment-53939244
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19496/consoleFull)
for PR 2203 at commit
[`b671f67`](https://github.com/a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2212#issuecomment-53939349
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 pro
GitHub user benoyantony opened a pull request:
https://github.com/apache/spark/pull/2212
[SPARK-3287] When ResourceManager High Availability is enabled, Applicat...
...ionMaster webUI is not displayed
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2208#issuecomment-53939346
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19499/consoleFull)
for PR 2208 at commit
[`fb26de8`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2211#issuecomment-53939974
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19505/consoleFull)
for PR 2211 at commit
[`42bd626`](https://github.com/ap
Github user benoyantony commented on a diff in the pull request:
https://github.com/apache/spark/pull/2206#discussion_r16925510
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -174,7 +174,7 @@ private[spark] class ApplicationMaster(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-53940609
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19498/consoleFull)
for PR 2209 at commit
[`a703ff4`](https://github.com/a
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2206#discussion_r16925624
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -174,7 +174,7 @@ private[spark] class ApplicationMaster(args:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2144#issuecomment-53941281
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19504/consoleFull)
for PR 2144 at commit
[`42fb5fa`](https://github.com/a
Github user xinyunh commented on the pull request:
https://github.com/apache/spark/pull/2099#issuecomment-53941443
I have made some changes according to the comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2205#issuecomment-53941658
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19502/consoleFull)
for PR 2205 at commit
[`f7b35be`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2211#issuecomment-53942264
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19505/consoleFull)
for PR 2211 at commit
[`42bd626`](https://github.com/a
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2099#issuecomment-53942469
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
ena
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2099#issuecomment-53942549
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19506/consoleFull)
for PR 2099 at commit
[`39f0309`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2099#issuecomment-53942584
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19506/consoleFull)
for PR 2099 at commit
[`39f0309`](https://github.com/a
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1612#issuecomment-53942630
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
ena
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1919#issuecomment-53942610
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
ena
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1612#issuecomment-53942746
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19508/consoleFull)
for PR 1612 at commit
[`917a753`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1919#issuecomment-53942774
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19507/consoleFull)
for PR 1919 at commit
[`0c324be`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1612#issuecomment-53942797
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19508/consoleFull)
for PR 1612 at commit
[`917a753`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1919#issuecomment-53942815
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19507/consoleFull)
for PR 1919 at commit
[`0c324be`](https://github.com/a
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/2213
[SPARK-3320][SQL] Made batched in-memory column buffer building work for
SchemaRDDs with empty partitions
You can merge this pull request into a Git repository by running:
$ git pull https:
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2213#issuecomment-53943074
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
ena
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2213#issuecomment-53943158
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19509/consoleFull)
for PR 2213 at commit
[`f67067d`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2213#issuecomment-53943337
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19510/consoleFull)
for PR 2213 at commit
[`f67067d`](https://github.com/ap
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2211#issuecomment-53943339
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 fea
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2193
---
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 enab
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/2193#issuecomment-53943566
LGTM. Merged into master and branch-1.1. (I skipped Jenkins because only
comments were modified.)
---
If your project is set up for it, you can reply to this email and ha
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2208#issuecomment-53943616
The build failure was caused by unrelated test suites.
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/2195#issuecomment-53943705
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 f
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2213#issuecomment-53943746
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19512/consoleFull)
for PR 2213 at commit
[`45a0139`](https://github.com/ap
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2189#issuecomment-53943840
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
en
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1778#issuecomment-53943844
@rezazadeh Could you update the PR to follow [Spark Code Style
Guide](https://cwiki.apache.org/confluence/display/SPARK/Spark+Code+Style+Guide)?
Thanks!
---
If your proj
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2195#issuecomment-53943920
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19513/consoleFull)
for PR 2195 at commit
[`792f009`](https://github.com/ap
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1698#issuecomment-53944079
@andy327 Do you mind closing this PR for now? I'm definitely buying the
idea of freeing up the master, but the current set of Core APIs doesn't provide
an easy and efficie
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1293#issuecomment-53944261
@viirya Do you mind closing this JIRA for now? We should handle this corner
case more gracefully. Instead of throwing an exception, we could output less
than k cluster cen
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2213#issuecomment-53944735
Ran tests locally. Going to merge speculatively so we can progress with
the 1.1 RCs.
---
If your project is set up for it, you can reply to this email and have your
re
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2213
---
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 enab
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2211#issuecomment-53945146
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 fea
201 - 300 of 332 matches
Mail list logo
