Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47302193
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16183/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302186
Build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302177
Build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47302192
Merged build finished.
---
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 adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277643
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -614,6 +614,8 @@ private[hive] object HiveQl {
queries.reduceLef
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302075
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/1151#issuecomment-47302051
This implementation is looking pretty complete. :)
A few testing and stylistic comments before we can merge this. Also please
merge with master.
---
If your p
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277596
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -614,6 +614,8 @@ private[hive] object HiveQl {
queries.reduceLeft(U
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277569
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -204,3 +204,17 @@ case class ExistingRdd(output: Seq[Attribute],
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277517
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -204,3 +204,17 @@ case class ExistingRdd(output: Seq[Attribute],
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277496
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -204,3 +204,17 @@ case class ExistingRdd(output: Seq[Attribute],
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277475
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -236,6 +236,8 @@ private[sql] abstract class SparkStrategies ex
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277491
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -204,3 +204,17 @@ case class ExistingRdd(output: Seq[Attribute],
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277468
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicOperators.scala
---
@@ -89,6 +89,13 @@ case class Join(
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47301712
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47301713
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47301718
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47301721
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
GitHub user colorant opened a pull request:
https://github.com/apache/spark/pull/1241
[SPARK-2288] Hide ShuffleBlockManager behind ShuffleManager
By Hiding the shuffleblockmanager behind Shufflemanager, we decouple the
shuffle data's block mapping management work from Diskblockmanan
Github user CodingCat closed the pull request at:
https://github.com/apache/spark/pull/1240
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47301657
Thanks, merged 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 does not have
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47301659
close temporarily
---
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/1190
---
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 witgo reopened a pull request:
https://github.com/apache/spark/pull/1112
SPARK-1291: Link the spark UI to RM ui in yarn-client mode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-1291
Alternatively
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/1112
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47301402
Merged build finished.
---
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/1240#issuecomment-47301404
Merged build finished.
---
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/1240#issuecomment-47301408
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16181/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47301407
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16180/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47301406
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16177/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47301403
Merged build finished. All automated tests passed.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1197#issuecomment-47301177
Thanks for confirming!
---
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 fe
Github user mattf closed the pull request at:
https://github.com/apache/spark/pull/1197
---
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 mattf commented on the pull request:
https://github.com/apache/spark/pull/1197#issuecomment-47301071
@rxin & @andrewor14 - i've confirmed that the patch for SPARK-2242 resolves
SPARK-2244. thanks for working with me on this!
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1200#issuecomment-47300366
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1200#issuecomment-47300373
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1226#issuecomment-47300075
Yeah, I don't know. Seems to work for me locally and you didn't touch
anything hive related...
test this please
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47299465
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47299472
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1227#discussion_r14276413
--- Diff: core/src/test/scala/org/apache/spark/MapOutputTrackerSuite.scala
---
@@ -24,6 +24,7 @@ import akka.testkit.TestActorRef
import org.scalatest
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/1226#issuecomment-47298915
@marmbrus I see, I will do it next time, thanks.
But why failed...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1200#discussion_r14276154
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -117,14 +117,25 @@ object SparkSubmit {
val isPython = args.isPython
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1200#discussion_r14276160
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -117,14 +117,25 @@ object SparkSubmit {
val isPython = args.isPython
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1200#discussion_r14276149
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -117,14 +117,25 @@ object SparkSubmit {
val isPython = args.isPython
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1200#discussion_r14276157
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -117,14 +117,25 @@ object SparkSubmit {
val isPython = args.isPython
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47297947
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47297942
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47297772
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16179/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47297771
Merged build finished.
---
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/1113#issuecomment-47297724
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47297683
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47297679
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-47297725
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16176/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47297356
Merged build finished.
---
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/1240#issuecomment-47297357
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16178/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47297168
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47297174
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/1240
SPARK-2126: Move MapOutputTracker behind ShuffleManager interface to
https://issues.apache.org/jira/browse/SPARK-2126
Move MapOutputTracker behind ShuffleManager interface to enable custo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47296613
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47296622
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47296531
Oh, code conflict.
---
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 th
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47296481
Thanks, updated.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1239#issuecomment-47295547
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16175/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1239#issuecomment-47295545
Merged build finished.
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-47295405
There's a typo in your title. :-)
Also, it could be shorter. Think that the PR title becomes the summary in
the final git commit, so it shows in commands like "git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-47295238
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/845#issuecomment-47295223
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 proj
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-47295220
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1239
---
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 closed the pull request at:
https://github.com/apache/spark/pull/1234
---
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/1239#issuecomment-47294935
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/1239
Strip '@' symbols when merging pull requests.
Currently all of the commits with '@X' in them cause person X to
receive e-mails every time someone makes a public fork of Spark.
@marmbrus
Github user elyast commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-47294545
so should I open another PR for master branch?
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1197#issuecomment-47294528
@mattf,
@andrewor14 has already committed the other fix (that fixes the two
separate issues) based on your feedback. I agree with you that the two issues
deserve se
Github user elyast commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-47294490
I have added more descriptive title
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1238#discussion_r14273921
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/LogicalPlan.scala
---
@@ -26,6 +26,18 @@ import org.apache.spark.sql.catalyst.
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1238#discussion_r14273941
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala ---
@@ -258,6 +263,19 @@ private[hive] case class MetastoreRelation
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1238#discussion_r14273901
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/LogicalPlan.scala
---
@@ -26,6 +26,18 @@ import org.apache.spark.sql.catalyst.
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1238#discussion_r14273785
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala ---
@@ -258,6 +263,19 @@ private[hive] case class MetastoreRelation
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1238#discussion_r14273776
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala ---
@@ -258,6 +263,19 @@ private[hive] case class MetastoreRelation
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1232#issuecomment-47293958
Yeah - the existing documentation is correct here, I think.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1238#discussion_r14273707
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala ---
@@ -245,7 +246,11 @@ object HiveMetastoreTypes extends RegexParsers {
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1238#discussion_r14273632
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/JoinSuite.scala ---
@@ -28,6 +29,14 @@ class JoinSuite extends QueryTest {
// Ensures tables are loa
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1238#discussion_r14273582
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -72,8 +72,9 @@ private[sql] abstract class SparkStrategies extends
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-47292702
Also, this should probably go into master before it goes to branch-1.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-47292613
Haven't looked at the code yet, but could you add a more descriptive title
to the PR? Thanks!
---
If your project is set up for it, you can reply to this email and have y
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1238#issuecomment-47292447
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16173/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1238#issuecomment-47292446
Merged build finished.
---
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/1238#issuecomment-47292249
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16174/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1238#issuecomment-47292247
Merged build finished.
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/1196#issuecomment-47292171
Looks ok, aside from the minor semantic issue above. The comment below
scares me a little bit:
If the user is null it is assumed authentication isn't turned o
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1238#issuecomment-47292122
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1238#issuecomment-47292134
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1236#issuecomment-47292088
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16172/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1236#issuecomment-47292086
Merged build finished. All automated tests passed.
---
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1196#discussion_r14272616
--- Diff: core/src/main/scala/org/apache/spark/SecurityManager.scala ---
@@ -169,18 +192,43 @@ private[spark] class SecurityManager(sparkConf:
SparkConf) exten
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1238#issuecomment-47291825
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1238#issuecomment-47291843
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
GitHub user concretevitamin opened a pull request:
https://github.com/apache/spark/pull/1238
[SQL] [WIP] Prototype implementation of size estimations for Catalyst
logical plans.
The idea is that every Catalyst logical plan gets hold of an Estimates
class, the usage of which provide
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1196#discussion_r14272505
--- Diff: core/src/main/scala/org/apache/spark/SecurityManager.scala ---
@@ -169,18 +192,43 @@ private[spark] class SecurityManager(sparkConf:
SparkConf) exten
101 - 200 of 421 matches
Mail list logo
