Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2511
---
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/2511#issuecomment-57590958
Thanks! Merged to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have t
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2357#issuecomment-57590659
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21183/consoleFull)
for PR 2357 at commit
[`609dd98`](https://github.com/ap
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/789#issuecomment-57590497
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/211
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-57590495
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2538#issuecomment-57590494
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
GitHub user ScrapCodes reopened a pull request:
https://github.com/apache/spark/pull/2357
[SPARK-3437][BUILD] Support crossbuilding in maven. With new
scala-install-plugin.
Since this plugin is not deployed anywhere, for anyone trying this patch
has to publish it locally by cloning
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2615#issuecomment-57590353
And this https://github.com/ScrapCodes/scala-install-plugin plugin takes
care of publishing correct poms too.
---
If your project is set up for it, you can reply to t
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2615#issuecomment-57590286
Hey Patrick, thanks for looking at this. I did not say it is not possible.
I just said the best(easiest ) way I could come up was to modify the maven
install plugin.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-57589906
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user jongyoul commented on the pull request:
https://github.com/apache/spark/pull/2126#issuecomment-57589522
@tgravescs This code only apples in mesos mode, so another mode - yarn and
standalone - is not affected.
+1 @timothysc,
val fwInfo =
FrameworkInfo.newB
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2501#issuecomment-57589474
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21178/consoleFull)
for PR 2501 at commit
[`65ed04a`](https://github.com/ap
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/789#issuecomment-57589292
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/211
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/789#issuecomment-57589288
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21175/consoleFull)
for PR 789 at commit
[`1be3fa5`](https://github.com/apa
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1893#issuecomment-57588918
@pwendell can you take a look at this when you have a chance
---
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/2502
---
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/476
---
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 enabl
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1375
---
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/2391
---
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/1486#issuecomment-57588340
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21177/consoleFull)
for PR 1486 at commit
[`338d4f8`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2620#issuecomment-57588338
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21176/consoleFull)
for PR 2620 at commit
[`caf25c6`](https://github.com/ap
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1486#issuecomment-57588159
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 hav
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-57588021
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21174/consoleFull)
for PR 2388 at commit
[`99945ce`](https://github.com/a
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2620#issuecomment-57588061
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-57588026
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/789#issuecomment-57585682
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21175/consoleFull)
for PR 789 at commit
[`1be3fa5`](https://github.com/apac
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/789#issuecomment-57585666
Updated patch allows using both at the same time
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proj
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2511#issuecomment-57584098
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21173/consoleFull)
for PR 2511 at commit
[`9fb973f`](https://github.com/a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2511#issuecomment-57584100
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-57584038
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21174/consoleFull)
for PR 2388 at commit
[`99945ce`](https://github.com/ap
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/2609#discussion_r18322230
--- Diff: core/src/main/scala/org/apache/spark/deploy/worker/Worker.scala
---
@@ -202,9 +205,20 @@ private[spark] class Worker(
// Spin up a separ
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2574#discussion_r18321787
--- Diff:
core/src/main/scala/org/apache/spark/ui/jobs/JobProgressPage.scala ---
@@ -70,11 +72,11 @@ private[ui] class JobProgressPage(parent:
JobProgressT
Github user ravipesala commented on the pull request:
https://github.com/apache/spark/pull/2590#issuecomment-57581369
Fixed code as per comments, please review
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proje
Github user mubarak closed the pull request at:
https://github.com/apache/spark/pull/1723
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user mubarak commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-57581072
Fixed using https://github.com/apache/spark/pull/2464
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2511#issuecomment-57580433
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21173/consoleFull)
for PR 2511 at commit
[`9fb973f`](https://github.com/ap
Github user zhzhan commented on the pull request:
https://github.com/apache/spark/pull/2241#issuecomment-57580447
@yhuai I removed all unnecessary implicits to make it consistent, but have
to keep wrapperToFileSinkDesc because HiveFileFormatUtils.getHiveRecordWriter
needs FileSinkDesc
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2511#discussion_r18321536
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -166,7 +186,7 @@ class SqlParser extends StandardTokenParsers wi
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2563#discussion_r18321520
--- Diff: python/pyspark/sql.py ---
@@ -385,50 +429,32 @@ def _parse_datatype_string(datatype_string):
>>> check_datatype(complex_maptype)
Tru
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-57579497
@buenrostro-oo @tdas We have seen several test failures from
`NetworkReceiverSuite`. Do you have time to take a look? Thanks!
---
If your project is set up for it, you ca
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2563#discussion_r18321352
--- Diff: python/pyspark/sql.py ---
@@ -205,6 +234,16 @@ def __str__(self):
return "ArrayType(%s,%s)" % (self.elementType,
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2563#discussion_r18321283
--- Diff: python/pyspark/sql.py ---
@@ -62,6 +63,12 @@ def __eq__(self, other):
def __ne__(self, other):
return not self.__eq__(other)
Github user scwf commented on a diff in the pull request:
https://github.com/apache/spark/pull/2576#discussion_r18321063
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/orc/OrcTableOperations.scala ---
@@ -0,0 +1,418 @@
+/*
+ * Licensed to the Apache Software Foundat
Github user scwf commented on a diff in the pull request:
https://github.com/apache/spark/pull/2576#discussion_r18321025
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/orc/OrcTableOperations.scala ---
@@ -0,0 +1,418 @@
+/*
+ * Licensed to the Apache Software Foundat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-57577580
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-57577573
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21171/consoleFull)
for PR 2595 at commit
[`a0d9de3`](https://github.com/a
Github user scwf commented on a diff in the pull request:
https://github.com/apache/spark/pull/2576#discussion_r18320990
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/orc/ORCQuerySuite.scala ---
@@ -0,0 +1,184 @@
+/*
+ * Licensed to the Apache Software Foundation (
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2620#issuecomment-57576395
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2541#discussion_r18320642
--- Diff: sbin/spark-config.sh ---
@@ -33,7 +33,7 @@ this="$config_bin/$script"
export SPARK_PREFIX="`dirname "$this"`"/..
export SPARK_HOME=
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2592#issuecomment-57575171
Yes, it should go after the DP PR.
---
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/1717#issuecomment-57575122
Do you mind adding "closes #2098" to the description of your PR so that
this automatically closes the other PR when merged? Thanks!!
---
If your project is set up for
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-57575023
Hi @mubarak,
This issue has been fixed by #2464, so do you mind closing this? Thanks!
(Due to the way that this GitHub mirror is set up, we don't have p
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/2623#issuecomment-57574915
https://github.com/apache/spark/pull/2610
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1310#issuecomment-57574730
Hi @joyyoj,
Since this pull request doesn't show any code / changes, do you mind
closing it? Feel free to update / re-open if you have code that you'd like us
Github user zhzhan commented on the pull request:
https://github.com/apache/spark/pull/2241#issuecomment-57574745
@pwendell I think the packaging has some problem, probably in protobuf. I
ran some test suite, but cannot go through. With the original package, the test
is OK. Following
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2609#issuecomment-57573144
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2609#issuecomment-57573135
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21169/consoleFull)
for PR 2609 at commit
[`77a9de0`](https://github.com/a
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2337
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2337#issuecomment-57572402
I've given it some thought and I don't think that we should merge the more
general async. mechanism that I described in #2482. It had some confusing
semantics surround
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-57572266
Ok, I'll try to use LD_LIBRARY_PATH.
---
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 no
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-57572114
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21171/consoleFull)
for PR 2595 at commit
[`a0d9de3`](https://github.com/ap
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/789#issuecomment-57572019
I think it's better to do both and explain that there might be problems.
Otherwise users will see this new API and perhaps be surprised that their old
registrator is no lon
Github user JoshRosen closed the pull request at:
https://github.com/apache/spark/pull/2482
---
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 e
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2482#issuecomment-57572018
I'm going to close this for now. My approach has some confusing semantics
and may be more general than what most users need.
---
If your project is set up for it, you
Github user chouqin commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-57571761
`NetworkReceiverSuite` in spark-streaming has failed, it is not related to
this PR.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user chouqin commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-57571778
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/1980#issuecomment-57570323
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21165/consoleFull)
for PR 1980 at commit
[`a29ec86`](https://github.com/a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1980#issuecomment-57570330
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-57570180
@ScrapCodes Do you have any better idea for this issue?
---
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/2595#issuecomment-57570139
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-57570133
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21166/consoleFull)
for PR 2595 at commit
[`a0d9de3`](https://github.com/a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2501#issuecomment-57569132
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2501#issuecomment-57569130
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21170/consoleFull)
for PR 2501 at commit
[`bdf9a3f`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2609#issuecomment-57568876
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21169/consoleFull)
for PR 2609 at commit
[`77a9de0`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2501#issuecomment-57568818
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21170/consoleFull)
for PR 2501 at commit
[`bdf9a3f`](https://github.com/ap
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2535
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2609#issuecomment-57568072
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2609#issuecomment-57568070
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21168/consoleFull)
for PR 2609 at commit
[`7b7cae4`](https://github.com/a
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2535#issuecomment-57567934
This looks good to me. 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 not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2609#issuecomment-57567979
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21168/consoleFull)
for PR 2609 at commit
[`7b7cae4`](https://github.com/ap
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2609#issuecomment-57567664
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2609#issuecomment-57567662
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21167/consoleFull)
for PR 2609 at commit
[`a045620`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2609#issuecomment-57567579
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21167/consoleFull)
for PR 2609 at commit
[`a045620`](https://github.com/ap
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2610#issuecomment-57567022
Oops you're right.
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-57566803
Okay here are some thoughts and questions:
- I don't think it really matters that we can't handle `f1.f11 > f2.f22`
because we already don't know what do to if a use
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2339#issuecomment-57566795
> This patch adds the following public classes (experimental):
println(s"Failed to load main class $childMainClass.")
FYI: I believe I have these phantom new
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/2538#discussion_r18318446
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/api/python/PythonDStream.scala
---
@@ -0,0 +1,304 @@
+/*
+ * Licensed to the Apache Softwa
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2339#issuecomment-57566562
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/2538#discussion_r18318422
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/api/python/PythonDStream.scala
---
@@ -0,0 +1,304 @@
+/*
+ * Licensed to the Apache Softwa
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2339#issuecomment-57566559
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21163/consoleFull)
for PR 2339 at commit
[`43a69f0`](https://github.com/a
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/2538#discussion_r18318391
--- Diff: python/pyspark/streaming/tests.py ---
@@ -0,0 +1,532 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contribu
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1737#issuecomment-57566129
You are right that we would have to change the BinaryType to be a case
class instead to hold this information and then change the rest of the code to
deal with that. It
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-57565848
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21166/consoleFull)
for PR 2595 at commit
[`a0d9de3`](https://github.com/ap
Github user nchammas commented on a diff in the pull request:
https://github.com/apache/spark/pull/2606#discussion_r18318253
--- Diff: dev/run-tests-jenkins ---
@@ -84,42 +98,46 @@ function post_message () {
fi
}
+
+# We diff master...$ghprbActualCommit bec
Github user manishamde commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-57565744
@chouqin Sorry for the delay in my review. I will finish mine within the
next 24 hours.
---
If your project is set up for it, you can reply to this email and have you
Github user nchammas commented on a diff in the pull request:
https://github.com/apache/spark/pull/2606#discussion_r18318239
--- Diff: dev/run-tests-jenkins ---
@@ -84,42 +98,46 @@ function post_message () {
fi
}
+
+# We diff master...$ghprbActualCommit bec
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2606#issuecomment-57565606
cc @pwendell This PR is ready for review.
Here are examples of the messages posted when:
* [all tests
pass](https://github.com/apache/spark/pull/2606#issueco
Github user chouqin commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-57565298
@mengxr @jkbradley thanks for your comments, it can pass unit test now, do
you have any more suggestions?
---
If your project is set up for it, you can reply to this ema
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1980#issuecomment-57564475
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21165/consoleFull)
for PR 1980 at commit
[`a29ec86`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2561#issuecomment-57564269
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/250/consoleFull)
for PR 2561 at commit
[`430f5d1`](https://github.com/
1 - 100 of 564 matches
Mail list logo
