Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1976#issuecomment-52385056
/cc @mateiz for review (this is the issue I mentioned in #1799).
---
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/1975#issuecomment-52385147
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18660/consoleFull)
for PR 1975 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1632#issuecomment-52385166
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1632#issuecomment-52385196
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18662/consoleFull)
for PR 1632 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1948#issuecomment-52385225
Merging this one in master branch-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 project does
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1948
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1632#issuecomment-52385237
Pending Jenkins, this looks good to me. Committers, feel free to merge (or
I'll do it).
---
If your project is set up for it, you can reply to this email and have
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/1902#issuecomment-52385275
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1632#discussion_r16323402
--- Diff:
core/src/main/scala/org/apache/spark/network/ConnectionManager.scala ---
@@ -61,17 +62,17 @@ private[spark] class ConnectionManager(
var
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1632#discussion_r16323399
--- Diff:
core/src/main/scala/org/apache/spark/network/ConnectionManager.scala ---
@@ -652,19 +654,21 @@ private[spark] class ConnectionManager(
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1632#issuecomment-52385383
Actually, I retract my earlier LGTM; this needs a bit of user-facing
configuration documentation and I think there's a corner-case bug in how we
handle late-arriving
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1912#issuecomment-52385422
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52385431
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18661/consoleFull)
for PR 1845 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1978#issuecomment-52385449
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1912#issuecomment-52385516
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18666/consoleFull)
for PR 1912 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1978#issuecomment-52385513
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18665/consoleFull)
for PR 1978 at commit
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1845#discussion_r16323472
--- Diff: bin/utils.sh ---
@@ -17,9 +16,53 @@
# limitations under the License.
#
+# *
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/1632#discussion_r16323483
--- Diff:
core/src/main/scala/org/apache/spark/network/ConnectionManager.scala ---
@@ -652,19 +654,21 @@ private[spark] class ConnectionManager(
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1632#discussion_r16323500
--- Diff:
core/src/main/scala/org/apache/spark/network/ConnectionManager.scala ---
@@ -652,19 +654,21 @@ private[spark] class ConnectionManager(
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/1632#discussion_r16323512
--- Diff:
core/src/main/scala/org/apache/spark/network/ConnectionManager.scala ---
@@ -652,19 +654,21 @@ private[spark] class ConnectionManager(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1632#issuecomment-52385869
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18662/consoleFull)
for PR 1632 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1632#discussion_r16323524
--- Diff:
core/src/main/scala/org/apache/spark/network/ConnectionManager.scala ---
@@ -652,19 +654,21 @@ private[spark] class ConnectionManager(
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/1632#discussion_r16323528
--- Diff:
core/src/main/scala/org/apache/spark/network/ConnectionManager.scala ---
@@ -652,19 +654,21 @@ private[spark] class ConnectionManager(
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1976#issuecomment-52385999
Looks good to me, feel free to merge 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1976
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1845#discussion_r16323564
--- Diff: bin/utils.sh ---
@@ -17,9 +16,53 @@
# limitations under the License.
#
+# * *
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1977#issuecomment-52386192
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18667/consoleFull)
for PR 1977 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1978#issuecomment-52386347
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18665/consoleFull)
for PR 1978 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1912#issuecomment-52386383
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18666/consoleFull)
for PR 1912 at commit
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/1983
[WIP][SPARK-1405]Collapsed Gibbs sampling based Latent Dirichlet Allocation
This PR is based on @yinxusen's #476
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/1983#issuecomment-52386453
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18668/consoleFull)
for PR 1983 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-52386461
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18668/consoleFull)
for PR 1983 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1632#issuecomment-52386455
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18669/consoleFull)
for PR 1632 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/1886#issuecomment-52386627
Oh... Jenkins don't like me? :(
---
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/1983#issuecomment-52386656
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18670/consoleFull)
for PR 1983 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1977#issuecomment-52386913
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18667/consoleFull)
for PR 1977 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1886#issuecomment-52386926
Jenkins is indeed a little overloaded these days because of all those
passionate contributors like you :) But this time I think it's because this
branch can no longer
GitHub user sryza opened a pull request:
https://github.com/apache/spark/pull/1984
SPARK-3082. yarn.Client.logClusterResourceDetails throws NPE if requeste...
...d queue doesn't exist
You can merge this pull request into a Git repository by running:
$ git pull
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1970#issuecomment-52386996
/cc @andrewor14
@sarutak We also need to revert [changes made in
#1891](https://github.com/apache/spark/pull/1760#issuecomment-51875134) in this
PR.
---
If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1984#issuecomment-52387014
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18672/consoleFull)
for PR 1984 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/1886#issuecomment-52387046
@liancheng Thanks!
I'll rebase this PR and I'll try to make start-thriftserver.sh to leverage
bin/utils.sh.
---
If your project is set up for it, you can reply to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1886#issuecomment-52387480
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18673/consoleFull)
for PR 1886 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1886#issuecomment-52388434
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18673/consoleFull)
for PR 1886 at commit
Github user iven commented on the pull request:
https://github.com/apache/spark/pull/1969#issuecomment-52388625
@JoshRosen I'm using Spark 1.0.1 with Mesos. If I don't specify SPARK_HOME
in the driver, Mesos executors will LOST with error:
```
sh:
Github user iven commented on the pull request:
https://github.com/apache/spark/pull/1969#issuecomment-52388869
@andrewor14 OK. I've update the patch when we confirm this PR is necessary.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/1977#issuecomment-52393277
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1977#issuecomment-52393443
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18674/consoleFull)
for PR 1977 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1977#issuecomment-52394905
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18674/consoleFull)
for PR 1977 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/1985
[SPARK-3077] fix unnecessarily removing sendingConnection when closing
connections
Currently in `ConnectionManager`, when a `ReceivingConnection` is closing,
the corresponding `SendingConnection`
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1985#issuecomment-52395214
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 mridulm commented on the pull request:
https://github.com/apache/spark/pull/1946#issuecomment-52395698
Thanks for digging into this !
From what I see, this is an implementation detail of a specific jdk version
(order in which syscall returns and order in which
GitHub user scwf opened a pull request:
https://github.com/apache/spark/pull/1986
[SPARK-2608] fix executor backend launch commond over mesos mode
https://issues.apache.org/jira/browse/SPARK-2608
This is the updated version of https://github.com/apache/spark/pull/1513
Github user scwf closed the pull request at:
https://github.com/apache/spark/pull/1513
---
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/1986#issuecomment-52396653
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/1689#issuecomment-52397817
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18675/consoleFull)
for PR 1689 at commit
GitHub user PeterDaveHello opened a pull request:
https://github.com/apache/spark/pull/1987
make CI build faster
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PeterDaveHello/spark patch-1
Alternatively you can review and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1988#issuecomment-52398042
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 PeterDaveHello opened a pull request:
https://github.com/apache/spark/pull/1988
make CI build faster
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PeterDaveHello/spark patch-2
Alternatively you can review and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1987#issuecomment-52398043
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 freeman-lab commented on the pull request:
https://github.com/apache/spark/pull/1952#issuecomment-52398080
@mengxr this looks great, will be simpler than writing custom loaders,
especially for streaming where there are so many possible input sources.
---
If your project
Github user PeterDaveHello closed the pull request at:
https://github.com/apache/spark/pull/1988
---
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 PeterDaveHello commented on the pull request:
https://github.com/apache/spark/pull/1988#issuecomment-52399641
duplicated with #1987, sorry
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1689#issuecomment-52400243
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18675/consoleFull)
for PR 1689 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1855#discussion_r16325942
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/parquet/ParquetTypes.scala ---
@@ -403,7 +406,10 @@ private[parquet] object ParquetTypesConverter
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1925#issuecomment-52401882
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1925
---
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 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1819#discussion_r16326189
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/parquet/ParquetMetastoreSuite.scala
---
@@ -0,0 +1,138 @@
+
+/*
+ * Licensed to the
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1974#issuecomment-52403590
LGTM - thanks for cleaning up the un-used code also. Let's see how this
goes.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1974
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1974#issuecomment-52403914
I merged this and bumped the timeout here to 120m and bumped the
Jenkins-side timeout to 130m
---
If your project is set up for it, you can reply to this email and
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-52404031
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1962#issuecomment-52404091
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-52404144
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18676/consoleFull)
for PR 1968 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1962#issuecomment-52404151
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18677/consoleFull)
for PR 1962 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1819#issuecomment-52404599
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18678/consoleFull)
for PR 1819 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1971#issuecomment-52404738
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1942#issuecomment-52404753
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1971#issuecomment-52404763
I haven't actually made any change since we reverted it, so expecting this
to timeout.
---
If your project is set up for it, you can reply to this email and have your
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1971#issuecomment-52404817
yeah I wanted to test our new timeout code - but since it doesn't merge
cleanly it won't test it anyways :P
---
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/1942#issuecomment-52404829
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18680/consoleFull)
for PR 1942 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1971#issuecomment-52404832
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18679/consoleFull)
for PR 1971 at commit
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/1974#issuecomment-52404851
Sounds good!
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1971#issuecomment-52405056
Ok I pushed a new version that merges cleanly. You should be able to use
this to test.
---
If your project is set up for it, you can reply to this email and have your
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1987#issuecomment-52405072
Actually I don't think we are using travis. We should probably remove that
file.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1819#issuecomment-52405086
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18681/consoleFull)
for PR 1819 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1819#issuecomment-52405112
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18681/consoleFull)
for PR 1819 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1971#issuecomment-52405176
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18682/consoleFull)
for PR 1971 at commit
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/1979#issuecomment-52405587
It's a shorter name, and I understand the concern about the confusion.
Looks good to me!
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-52405893
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18676/consoleFull)
for PR 1968 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1962#issuecomment-52405928
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18677/consoleFull)
for PR 1962 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1632#issuecomment-52406146
I've merged this to `master` and `branch-1.1`. 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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1632
---
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/1942#issuecomment-52406287
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18680/consoleFull)
for PR 1942 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1819#issuecomment-52406347
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18678/consoleFull)
for PR 1819 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1890#issuecomment-52407167
Hey @GrahamDennis thanks for an extremely thorough analysis of this issue
here and on the JIRA. I think that @rxin was able to solve this in a PR that
improves the way
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1952#issuecomment-52407340
@freeman-lab Thanks for reviewing! I've merged this into master and
branch-1.1.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1952
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1979
---
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/1979#issuecomment-52407359
@brkyvz Thanks for reviewing! I've merged this into master and branch-1.1.
---
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/1971#issuecomment-52407838
**Tests timed out** after a configured wait of `120m`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
1 - 100 of 171 matches
Mail list logo
