Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39661196
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/274#issuecomment-39661222
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13816/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39661221
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/274#issuecomment-39661256
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/274#issuecomment-39661265
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 rezazadeh opened a pull request:
https://github.com/apache/spark/pull/336
Dimension Independent Similarity Computation
Provide Implementation of DIMSUM for squaring a Tall and Skinny Matrix as
described in: http://arxiv.org/abs/1304.1467
Also, refactor Matrix
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/336#issuecomment-39661825
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/336#issuecomment-39661827
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/336#issuecomment-39661853
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/336#issuecomment-39661854
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13818/
---
If your project is set up for it, you can
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/337
[SPARK-1429] Spark shell fails to start after sbt clean assemble-deps
package
JIRA issue: [SPARK-1429](https://issues.apache.org/jira/browse/SPARK-1429)
Spark shell fails to start after
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/337#issuecomment-39662669
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/337#issuecomment-39662671
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 mridulm commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39663561
Hi @pwendell, Can you please mark
* core/src/main/scala/org/apache/spark/util/collection/AppendOnlyMap.scala
*
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/337#issuecomment-39663619
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13819/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/337#issuecomment-39663618
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/266#discussion_r11325597
--- Diff:
core/src/main/scala/org/apache/spark/util/collection/OpenHashMap.scala ---
@@ -26,8 +26,7 @@ import scala.reflect.ClassTag
*
* Under the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/291#issuecomment-39666122
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/291#issuecomment-39666117
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/291#issuecomment-39667203
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 haosdent commented on the pull request:
https://github.com/apache/spark/pull/194#issuecomment-39667634
@marmbrus @pwendell Could you help me review this pull request again? I
have already add `saveAsHBaseTable(rdd: SchemaRDD ...)` method. Thank you in
advance.
---
If
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/322#issuecomment-39674063
Hey @ueshin @manku-timma - as a simpler fix, would it be possible to just
change the way SparkEnv captures the class loader? I think it was probably just
an oversight
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/337#issuecomment-39674101
This check assumes the existence of the -hive- jars, which #237 is removing.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39674190
Addressed comments and removed WIP.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39674358
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 aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/237#discussion_r11327251
--- Diff: bin/compute-classpath.sh ---
@@ -59,7 +45,7 @@ if [ -f $ASSEMBLY_DIR/spark-assembly*hadoop*-deps.jar
]; then
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39675354
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39675896
Its not a matter of the if statements inside of spark logging code. Scala
logging rewrites your log statements to put the if checks _inline_ with _every_
logging
Github user manku-timma commented on the pull request:
https://github.com/apache/spark/pull/322#issuecomment-39676303
@pwendell: I tested your fix to SparkEnv.scala (after reverting my earlier
change). It does not work. SparkEnv's loader turns out to be
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39676694
Very similar to what I was thinking @marmbrus -- but you wrote it up more
completely than I would have. This is also why I've been moving some
performance-critical
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39676691
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/274#issuecomment-39676695
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/322#issuecomment-39676705
Another way of putting my question. Currently there is a line:
```
Thread.currentThread.setContextClassLoader(getClass.getClassLoader)
```
What is the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39676925
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13822/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39676924
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39677214
The thing is - adding a dependency is not free. It means that everyone who
packages spark downstream needs to deal with a bunch of annoying stuff. For
instance, this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39677446
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/274#issuecomment-39677440
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/274#issuecomment-39677764
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39677846
@witgo could you take a crack at doing that? I think it would be a fairly
small change to `Logging.scala` where we just use the scala-logging wrapper
instead of the
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39677875
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/266#issuecomment-39677970
For the OpenHashMap null lower bound, it should be fine to drop the lower
bound (based on my 30 sec check).
The original intention was that if the key is primitive
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39679070
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13823/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39679498
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. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39679499
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13824/
---
If your project
GitHub user dgshep opened a pull request:
https://github.com/apache/spark/pull/338
In the contex of SPARK-1337: Make sure that all metadata fields are
properly cleaned
While working on spark-1337 with @pwendell, we noticed that not all of the
metadata maps in JobProgessListener
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/338#discussion_r11328347
--- Diff:
core/src/main/scala/org/apache/spark/ui/jobs/JobProgressListener.scala ---
@@ -92,8 +91,10 @@ private[ui] class JobProgressListener(conf:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/339#issuecomment-39685393
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/339#issuecomment-39685394
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/339#issuecomment-39685520
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/339#issuecomment-39685517
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/339#issuecomment-39685648
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/339#issuecomment-39685649
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13825/
---
If your project is set up for it, you can
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/333#issuecomment-39686245
Thanks, merged.
---
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/291#discussion_r11328543
--- Diff: pom.xml ---
@@ -54,11 +54,11 @@
/developers
issueManagement
systemJIRA/system
-
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/291#discussion_r11328562
--- Diff: pom.xml ---
@@ -810,7 +814,6 @@
plugin
groupIdorg.apache.maven.plugins/groupId
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/291#issuecomment-39686424
Looks great! Two very minor comments/questions.
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/291#discussion_r11328579
--- Diff: pom.xml ---
@@ -810,7 +814,6 @@
plugin
groupIdorg.apache.maven.plugins/groupId
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/333
---
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/156#issuecomment-39687170
Merged, 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 have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/339#issuecomment-39687618
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/339#issuecomment-39687619
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13826/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/296#issuecomment-39687713
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/291#issuecomment-39688554
Okay I'm just gonna merge this with a minor doc change.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/267#issuecomment-39688636
Thanks, merged.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39688763
Thanks a lot for looking at this Aaron, I've merged it.
---
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/296#issuecomment-39689161
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/296#issuecomment-39689162
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13827/
---
If your project
Github user manku-timma commented on the pull request:
https://github.com/apache/spark/pull/322#issuecomment-39689262
@pwendell: You are right. Actually
`sun.misc.Launcher$AppClassLoader@12360be0` is the classloader even in the
earlier code.
Looks like classes directly
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/339#issuecomment-39689629
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13828/
---
If your project
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/340
[sql] Rename Expression.apply to eval for better readability.
I didn't rename the table generator function yet - we might want a
different name for those.
You can merge this pull request into a Git
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/340#issuecomment-39689824
@marmbrus I was looking over the code. How come we have a default
implementation for the Expression.eval/apply? Don't we want a concrete
expression implementation to fail if
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/340#issuecomment-39689858
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/340#issuecomment-39689853
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/237
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/267
---
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/336#issuecomment-39690309
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/336#issuecomment-39690310
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/288#issuecomment-39691483
I just went ahead and fixed the conflict and merged this.
---
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 velvia commented on the pull request:
https://github.com/apache/spark/pull/288#issuecomment-39691647
Thanks Patrick!
-Evan
To be free is not merely to cast off one's chains, but to live in a way
that respects enhances the freedom of others. (#NelsonMandela)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/340#issuecomment-39691697
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/336#issuecomment-39691696
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/340#issuecomment-39691699
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13829/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/336#issuecomment-39691698
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13830/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/288
---
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/341#issuecomment-39691939
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/341#issuecomment-39691933
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/341#issuecomment-39692088
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/342#issuecomment-39692525
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/342#issuecomment-39692528
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/126#issuecomment-39692913
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/126#issuecomment-39692914
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13834/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/341#issuecomment-39693022
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/341#issuecomment-39693204
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13832/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/342#issuecomment-39694139
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13833/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/342#issuecomment-39694137
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/342#issuecomment-39694667
Okay merged this. I tested it earlier to merge a conflicting pr.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39694787
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39694872
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/332#issuecomment-39694868
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
1 - 100 of 115 matches
Mail list logo
