Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1257#issuecomment-47448132
@pwendell why 1 then? Like why not 1000, or 1M?
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1261#issuecomment-47448784
Preview of the change:
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/1261
[SPARK-2320] Reduce exception/code block font size in web ui
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark ui-pre-size
Alternatively
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/1262
[SPARK-2299] Consolidate various stageIdTo* hash maps in JobProgressListener
This should reduce memory usage for the web ui as well as slightly increase
its speed in draining the UI event queue.
You
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1262#issuecomment-47448815
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1261#issuecomment-47448816
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1262#issuecomment-47448820
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1261#issuecomment-47448819
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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1262#discussion_r14328143
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/StagePage.scala ---
@@ -67,28 +61,28 @@ private[ui] class StagePage(parent: JobProgressTab)
extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1262#issuecomment-47449638
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.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1261#issuecomment-47449641
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16241/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1261#issuecomment-47449639
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.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1262#issuecomment-47449640
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16240/
---
If your
Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/1216#issuecomment-47449894
lgtm
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-47453099
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-47453105
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-47453145
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 have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-47453146
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16242/
---
If your project is set up for it, you can
Github user willb commented on a diff in the pull request:
https://github.com/apache/spark/pull/143#discussion_r14329726
--- Diff: core/src/main/scala/org/apache/spark/util/ClosureCleaner.scala ---
@@ -153,6 +153,18 @@ private[spark] object ClosureCleaner extends Logging {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47458467
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47458471
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/143#issuecomment-47459527
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16243/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47459526
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
Github user willb commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47459912
Sorry, I missed FailureSuite. I have a fix but ran out of battery before I
could push.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47460336
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/143#issuecomment-47460329
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47462979
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.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47462980
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16244/
---
If your project
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/1263
[SPARK-2059][SQL] Add analysis checks
An initial version of analysis checks. Long term we are going to want
something more complete, but this at least prevents us from making it all the
way
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1263#issuecomment-47467036
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1263#issuecomment-47467023
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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/143#discussion_r14331097
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/DStream.scala ---
@@ -533,7 +533,7 @@ abstract class DStream[T: ClassTag] (
* on
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/143#discussion_r14331096
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/DStream.scala ---
@@ -533,7 +533,7 @@ abstract class DStream[T: ClassTag] (
* on
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1263#discussion_r14331223
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -20,6 +20,7 @@ package
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1263#discussion_r14331240
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -54,10 +55,22 @@ class Analyzer(catalog: Catalog, registry:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1263#issuecomment-47473283
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16245/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1263#issuecomment-47473282
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1263#issuecomment-47475165
Maybe also add a test case?
---
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/962#issuecomment-47478084
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/962#issuecomment-47478075
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47480391
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47480392
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16246/
---
If your project is set up for it, you can
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47480476
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1261#issuecomment-47480528
LGTM. We could add a `+show stack trace` button later so it doesn't cram
all the other columns to the left. (similar to `+show details` on the index
page)
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47480644
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/962#issuecomment-47480635
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
Github user YanjieGao commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47480949
Hi all, I have modify the files and update the code as your
suggestiones.The build has triggered but it didn't merged . I don't know what's
the main cause of didn't
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47482971
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16247/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47482970
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.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1261
---
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/1261#issuecomment-47483890
That's a good idea. Let's do that next.
Merging this in master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/1264
[SPARK-2322] Exception in resultHandler could crash DAGScheduler and
shutdown SparkContext.
This should go into 1.0.1.
You can merge this pull request into a Git repository by running:
$ git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1264#issuecomment-47484375
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1264#issuecomment-47484383
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47484638
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/962#issuecomment-47484629
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1264#issuecomment-47484945
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1264#issuecomment-47484947
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16248/
---
If your project is set up for it, you can
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1264#issuecomment-47484978
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 rxin opened a pull request:
https://github.com/apache/spark/pull/1265
[SPARK-2059][SQL] Add analysis checks
This replaces #1263 with a test case.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1265#issuecomment-47485148
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user marmbrus closed the pull request at:
https://github.com/apache/spark/pull/1263
---
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/1265#issuecomment-47485201
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1265#issuecomment-47485210
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
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/1017#issuecomment-47485261
Ping @rxin, are you concerned about too much logging? I can lower the
level if you think this adds too much.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1017#issuecomment-47486375
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1017#issuecomment-47486383
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
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/1245#discussion_r14333421
--- Diff: core/src/main/scala/org/apache/spark/Partitioner.scala ---
@@ -96,15 +98,15 @@ class HashPartitioner(partitions: Int) extends
Partitioner {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1264#issuecomment-47489009
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16251/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1265#issuecomment-47489004
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1265#issuecomment-47489006
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16250/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1017#issuecomment-47489007
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16252/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47489002
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1017#issuecomment-47489005
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.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47489008
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16249/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1264#issuecomment-47489003
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.
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/1264#discussion_r14333837
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -838,7 +839,16 @@ class DAGScheduler(
Github user li-zhihui commented on the pull request:
https://github.com/apache/spark/pull/900#issuecomment-47490304
@tgravescs @kayousterhout
It will lead to a logic deadlock in yarn-cluster mode, if waitBackendReady
is in TaskSchedulerImpl.start.
How about move it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47491606
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47492104
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47492111
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47492633
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47492785
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47492790
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/1241#issuecomment-47493566
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47493571
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
Github user colorant commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47493840
@rxin Moved getBlockLocation method from shuffleBlockManager to
HashShuffleBlockMananger to make the interface more general. Does current
interface looks reasonable for
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/962
---
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 kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47495017
I've merged this into master (the Jenkins build finished but got stuck
behind another broken build to report success). @sryza I added a comment as you
suggested; we
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1245#issuecomment-47495454
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1245#issuecomment-47495446
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47495499
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16256/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47495497
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16253/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47495494
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47495495
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.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47495493
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47495500
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16255/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47495496
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.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-47495498
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16254/
---
If your project
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/962#issuecomment-47495559
oops you guys beat me to 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 does not have
1 - 100 of 110 matches
Mail list logo
