Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1990#issuecomment-52414552
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 scwf commented on the pull request:
https://github.com/apache/spark/pull/1992#issuecomment-52414632
@markhamstra, thanks for comments. I have merged SecurityManager right now
and updated with your comments.
---
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/1997#issuecomment-52414858
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18695/consoleFull)
for PR 1997 at commit
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/1946#issuecomment-52414914
Not sure, https://bugs.openjdk.java.net/browse/JDK ?
On Sun, Aug 17, 2014 at 8:54 AM, å¶å
è¿ notificati...@github.com wrote:
@mridulm
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1975#issuecomment-52414976
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18697/consoleFull)
for PR 1975 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1993#issuecomment-52415064
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18696/consoleFull)
for PR 1993 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1975#issuecomment-52415104
Merged into 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. If your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1975
---
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 the pull request:
https://github.com/apache/spark/pull/1987#issuecomment-52415339
Yea. It was an experiment we did, but we never really used it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/1878#issuecomment-52416428
@mengxr Thanks for the comments! Updated accordingly.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1878#issuecomment-52416455
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18700/consoleFull)
for PR 1878 at commit
Github user PeterDaveHello closed the pull request at:
https://github.com/apache/spark/pull/1987
---
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/1987#issuecomment-52416652
Okay, then I'll close this 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1878#issuecomment-52417298
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18700/consoleFull)
for PR 1878 at commit
GitHub user scwf opened a pull request:
https://github.com/apache/spark/pull/1998
[SPARK-3088] fix noisy messages when run tests
There are quite noisy messages when jekins run tests with maven or sbt. For
example , see from this link:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1998#issuecomment-52417541
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/1970#issuecomment-52419220
I've reverted my previous changes in #1891 .
---
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/1970#issuecomment-52419254
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18701/consoleFull)
for PR 1970 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-52419415
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18702/consoleFull)
for PR 1983 at commit
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-52419470
How about record the `(stageId,partitionId)` in `Accumulable `?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-52419524
I will resubmit the PR next week, as DAGScheduler has been changed a lot in
the passed months
---
If your project is set up for it, you can reply to this email and
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/1998#issuecomment-52419964
Hm, wouldn't this suppress a lot of important info from the build though?
Like errors and such.
---
If your project is set up for it, you can reply to this email and
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1962#issuecomment-52420059
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/1962#issuecomment-52420144
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18703/consoleFull)
for PR 1962 at commit
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/1998#issuecomment-52420276
@srowen , Actually it suppress some no used info when running test, the
test info and error will not be suppressed.
---
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/1983#issuecomment-52420410
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18702/consoleFull)
for PR 1983 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1970#issuecomment-52420539
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18701/consoleFull)
for PR 1970 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1962#issuecomment-52421588
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18703/consoleFull)
for PR 1962 at commit
Github user shane-huang commented on a diff in the pull request:
https://github.com/apache/spark/pull/1907#discussion_r16329942
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -86,13 +89,25 @@ private[spark] class BlockManager(
new
Github user shane-huang commented on the pull request:
https://github.com/apache/spark/pull/1907#issuecomment-52424278
Thanks for re-implementing this. Really nice to see this working :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user kanzhang commented on a diff in the pull request:
https://github.com/apache/spark/pull/1845#discussion_r16330493
--- Diff: bin/utils.sh ---
@@ -17,9 +16,53 @@
# limitations under the License.
#
+# *
Github user kayousterhout closed the pull request at:
https://github.com/apache/spark/pull/1762
---
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
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/1999
SPARK-2881: Upgrade to Snappy 1.0.5.3 to avoid SPARK-2881.
This version of Snappy was releases with a backported fix specifically
for Spark. This fixes an issue where names collide in the
Github user pwendell closed the pull request at:
https://github.com/apache/spark/pull/1994
---
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/1994#issuecomment-52428656
I'm closing this in favor of #1999
---
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/1878#issuecomment-52428670
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18704/consoleFull)
for PR 1878 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1999#issuecomment-52428822
QA tests have started for PR 1999. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18705/consoleFull
---
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/2000
[SPARK-3089] Make error message in ConnectionManager more meaningful
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sarutak/spark SPARK-3089
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2000#issuecomment-52429833
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18706/consoleFull)
for PR 2000 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1878#issuecomment-52430001
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18704/consoleFull)
for PR 1878 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1999#issuecomment-52430827
QA results for PR 1999:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2000#issuecomment-52431334
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18706/consoleFull)
for PR 2000 at commit
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/2001
[SPARK-3090] Add shutdown hook to stop SparkContext for YARN Client mode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sarutak/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2001#issuecomment-52432213
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18707/consoleFull)
for PR 2001 at commit
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/2002
[SPARK-2974] [SPARK-2975] Fix two bugs related to spark.local.dirs
This PR fixes two bugs related to `spark.local.dirs` and
`SPARK_LOCAL_DIRS`, one where `Utils.getLocalDir()` might return an
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2002#issuecomment-52433120
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18708/consoleFull)
for PR 2002 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2002#discussion_r16331781
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -451,10 +451,56 @@ private[spark] object Utils extends Logging {
/**
*
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2002#issuecomment-52433275
/cc @YanTangZhai, who has a similar PR to address one of these issues
(#1281) and who added the patch that ignores invalid local directories (#1274).
---
If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2001#issuecomment-52433847
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18707/consoleFull)
for PR 2001 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2002#issuecomment-52434839
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18708/consoleFull)
for PR 2002 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/1878#issuecomment-52435269
@mengxr It looks like the failures are in other tests; how best to
proceed? With respect to the case class Params, is it OK to have them public
since they are in
GitHub user Ishiihara opened a pull request:
https://github.com/apache/spark/pull/2003
[SPARK-2842][MLlib]Word2Vec documentation
Documentation for Word2Vec
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Ishiihara/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2003#issuecomment-52437105
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18709/consoleFull)
for PR 2003 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1995#issuecomment-52438069
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1999#issuecomment-52438082
This failure is a known issue with the thriftserver. All other tests are
okay, so I'm merging this.
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1995#issuecomment-52438146
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18710/consoleFull)
for PR 1995 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2003#issuecomment-52438525
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18709/consoleFull)
for PR 2003 at commit
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/2004
[SQL] Improve debug logging and toStrings.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marmbrus/spark codgenDebugging
Alternatively you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2004#issuecomment-52438737
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18711/consoleFull)
for PR 2004 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1937#issuecomment-52438819
@tianyi it might make more sense to handle this in the physical execution
of `SetCommand`, I'll see if I can do that. The local property is necessary I
think - do you
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1937#issuecomment-52439161
@tianyi after looking some more, I believe this needs to be handled in the
thriftserver explicitly and cannot be handled in the `SetCommand` physical
operator. The
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1937#issuecomment-52439377
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/1937#issuecomment-52439493
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18713/consoleFull)
for PR 1937 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1995#issuecomment-52439564
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18710/consoleFull)
for PR 1995 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1937#issuecomment-52439575
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18713/consoleFull)
for PR 1937 at commit
GitHub user mateiz opened a pull request:
https://github.com/apache/spark/pull/2005
[SPARK-3091] [SQL] Add support for caching metadata on Parquet files
For larger Parquet files, reading the file footers (which is done in
parallel on up to 5 threads) and HDFS block locations (which
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1937#issuecomment-52439878
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18715/consoleFull)
for PR 1937 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2005#issuecomment-52439880
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18714/consoleFull)
for PR 2005 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1995#issuecomment-52440162
Okay merging this upgrade.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1995
---
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/2005#issuecomment-52440481
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18716/consoleFull)
for PR 2005 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2004#issuecomment-52440599
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18711/consoleFull)
for PR 2004 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2005#issuecomment-52440757
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18717/consoleFull)
for PR 2005 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1935#issuecomment-52441076
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18718/consoleFull)
for PR 1935 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1935#issuecomment-52441094
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18718/consoleFull)
for PR 1935 at commit
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/2006
SPARK-3092: Always include the thriftserver when -Phive is enabled.
Currently we have a separate profile called hive-thriftserver. I originally
suggested this in case users did not want to bundle
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1944#issuecomment-52441264
Sounds good - it will also conflict (logically) with #2006
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2006#issuecomment-52441333
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18719/consoleFull)
for PR 2006 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1937#issuecomment-52441880
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18715/consoleFull)
for PR 1937 at commit
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/2007
Revert [SPARK-2970] [SQL] spark-sql script ends with IOException when
EventLogging is enabled
Revert #1891 due to issues with hadoop 1 compatibility.
You can merge this pull request into a Git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2007#issuecomment-52442134
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18720/consoleFull)
for PR 2007 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2007
---
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/1935#issuecomment-52442483
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18721/consoleFull)
for PR 1935 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1935#issuecomment-52442594
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18721/consoleFull)
for PR 1935 at commit
Github user tianyi commented on the pull request:
https://github.com/apache/spark/pull/1937#issuecomment-52442836
@pwendell thanks for the explanation. I think there should be some test
case about this feature.
---
If your project is set up for it, you can reply to this email and
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/1970#issuecomment-52443011
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/2005#issuecomment-52442999
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18717/consoleFull)
for PR 2005 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2006#issuecomment-52443146
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18719/consoleFull)
for PR 2006 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1970#issuecomment-52443217
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18722/consoleFull)
for PR 1970 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1935#issuecomment-52443395
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18723/consoleFull)
for PR 1935 at commit
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-52443825
Jenkins, this is 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
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/1723#discussion_r16334743
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -813,7 +816,10 @@ private[spark] object Utils extends Logging {
* A regular
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-52443994
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18724/consoleFull)
for PR 1723 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2004#issuecomment-52444010
This only failed hive-thriftserver. I'm going to merge into master and 1.1
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-52444020
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18724/consoleFull)
for PR 1723 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2004
---
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/1993#discussion_r16334783
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins.scala ---
@@ -19,16 +19,15 @@ package org.apache.spark.sql.execution
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1819#issuecomment-52444171
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18725/consoleFull)
for PR 1819 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/1723#discussion_r16334830
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/StreamingContext.scala ---
@@ -38,7 +38,7 @@ import org.apache.spark.streaming.dstream._
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/1723#discussion_r16334866
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/DStream.scala ---
@@ -106,6 +106,27 @@ abstract class DStream[T: ClassTag] (
/**
1 - 100 of 161 matches
Mail list logo
