Github user jyotiska commented on a diff in the pull request:
https://github.com/apache/spark/pull/83#discussion_r10330490
--- Diff: docs/python-programming-guide.md ---
@@ -146,7 +146,7 @@ sc = SparkContext(conf = conf)
# API Docs
-[API documentation](api/pyspa
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/86#discussion_r10330438
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkAppArguments.scala ---
@@ -0,0 +1,155 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36818916
what? how to understand the output? no failure, but there are some
exceptions in the console output
Accumulator cannot be accessed inside task?
---
If your proj
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36818651
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 fea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36818662
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13011/
---
If your pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36818661
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 have t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36818653
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13012/
---
If your pr
Github user etrain commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-36817253
This PR is the result of several iterations on the idea of wanting to build
fast decision trees for Spark.
To offer a little more color on the design here, the key
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/78
---
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 enable
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36815803
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 feat
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/70
---
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 enable
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36815759
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36815549
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 this f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36815535
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36815479
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13008/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36815476
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13009/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36815474
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 have t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36815477
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 fea
David,
There used to be standard BFGS testcases in Professor Nocedal's
package...did you stress test the solver with them ?
If not I will shoot him an email for them.
Thanks.
Deb
On Wed, Mar 5, 2014 at 2:00 PM, David Hall wrote:
> On Wed, Mar 5, 2014 at 1:57 PM, DB Tsai wrote:
>
> > Hi Dav
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36814645
@pwendell , I removed some redundant parameters, but I'm thinking that
which option is more convenient for the user, different pages contain different
set of parameters,
Github user markgrover commented on the pull request:
https://github.com/apache/spark/pull/78#issuecomment-36814000
Sure, we use that target for integrating Spark into the Apache Bigtop
distribution. In particular, we build a .tar.gz using the maven-assembly-plugin
and it contains all
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/78#issuecomment-36813430
Hey actually I'll just add this comment in the merge. I'll merge this into
master and 0.9 now.
---
If your project is set up for it, you can reply to this email and have
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36813427
@pwendell , yep, I asked in the mail list, but didn't get response, so I
decided to put the things here first and revise it (e.g. remove those
unnecessary) based on the f
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/78#issuecomment-36813329
@markgrover Thanks for addressing these issues. I actually didn't realize
that downstream integrator were using `maven dist` to build packages. Would you
mind adding a qui
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36813035
Hey @CodingCat not all of the configs in spark are meant to be externally
documented so we'll have to take a bit of time and look through this list.
Thanks for going throu
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/70#issuecomment-36812734
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 feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/86#issuecomment-36812637
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 have t
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36812678
I said it is WIP, because of 2 things
1. The document is surely need to be revised, I'm not sure if I understand
all details correctly, though I spent not so shor
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/86#issuecomment-36812638
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13010/
---
If your pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/86#issuecomment-36812535
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/86#issuecomment-36812536
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 th
GitHub user sryza opened a pull request:
https://github.com/apache/spark/pull/86
SPARK-1126. spark-app preliminary
This is a starting version of the spark-app script for running compiled
binaries against Spark. It still needs tests and some polish. The only
testing I've done so
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36812173
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36812172
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 have
GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/85
SPARK-1192: The document for most of the parameters used in core component
I grep the code in core component, I found that around 30 parameters in the
implementation is actually used but undocumente
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36811871
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 this f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/84#issuecomment-36811862
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 proje
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36811873
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 feat
GitHub user berngp opened a pull request:
https://github.com/apache/spark/pull/84
[SPARK-1186] : Enrich the Spark Shell to support additional arguments.
Enrich the Spark Shell functionality to support the following options.
```
Usage: spark-shell [OPTIONS]
OPTIO
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/63
---
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 enable
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/63#issuecomment-36800228
@kayousterhout Thank you very much!
---
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 kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/63#issuecomment-36799644
This looks good -- I've merged this 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 yo
On Wed, Mar 5, 2014 at 1:57 PM, DB Tsai wrote:
> Hi David,
>
> On Tue, Mar 4, 2014 at 8:13 PM, dlwh wrote:
> > I'm happy to help fix any problems. I've verified at points that the
> > implementation gives the exact same sequence of iterates for a few
> different
> > functions (with a particular
Hi David,
On Tue, Mar 4, 2014 at 8:13 PM, dlwh wrote:
> I'm happy to help fix any problems. I've verified at points that the
> implementation gives the exact same sequence of iterates for a few different
> functions (with a particular line search) as the c port of lbfgs. So I'm a
> little surpris
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/83#discussion_r10317227
--- Diff: docs/python-programming-guide.md ---
@@ -146,7 +146,7 @@ sc = SparkContext(conf = conf)
# API Docs
-[API documentation](api/pyspa
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/33#issuecomment-36781865
filed https://spark-project.atlassian.net/browse/SPARK-1191
---
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/33#issuecomment-36778996
@tgravescs Sure thing - but could you make the JIRA a blocker for Spark
1.0? It would be great if you could enumerate what assumptions are broken in
the current model (the
Tom,
I tried the command line you used and it didn't work for me.
On Fri, Feb 28, 2014 at 6:05 AM, Tom Graves wrote:
> what build command are you using?What do you mean when you say YARN
> branch?
>
> The yarn builds have been working fine for me with maven. Build command
> I use against
On Wed, Mar 5, 2014 at 8:50 AM, Debasish Das wrote:
> Hi David,
>
> Few questions on breeze solvers:
>
> 1. I feel the right place of adding useful things from RISO LBFGS (based on
> Professor Nocedal's fortran code) will be breeze. It will involve stress
> testing breeze LBFGS on large sparse dat
This would be extremely helpful if we can make this work. I know there's
also a ticket on Jira for making these options available in a configuration
file (or maybe extending the existing shell script):
https://spark-project.atlassian.net/browse/SPARK-529.
Thanks,
Benny
On Wed, Mar 5, 2014 at 9:
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/33#issuecomment-36764964
yes I haven't made that change yet. I should have a patch up in a few hours
with that changed. I'm just doing some finally testing on it. I'm changing it
to pass the sec
Hi David,
Few questions on breeze solvers:
1. I feel the right place of adding useful things from RISO LBFGS (based on
Professor Nocedal's fortran code) will be breeze. It will involve stress
testing breeze LBFGS on large sparse datasets and contributing fixes to
existing breeze LBFGS with the le
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/83#discussion_r10306693
--- Diff: docs/python-programming-guide.md ---
@@ -146,7 +146,7 @@ sc = SparkContext(conf = conf)
# API Docs
-[API documentation](api/pysp
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/33#issuecomment-36762448
Ah I see from your earlier comment that's still a "TODO" perhaps.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/33#issuecomment-36762162
Hey @tgravescs I noticed the `SecurityManager` still reads the system
properties directly. Any reason this can't be changed to take a `SparkConf` on
instantiation? The way
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/83#discussion_r10306225
--- Diff: docs/python-programming-guide.md ---
@@ -146,7 +146,7 @@ sc = SparkContext(conf = conf)
# API Docs
-[API documentation](api/pyspa
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/83#issuecomment-36760894
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13007/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/83#issuecomment-36760892
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 have t
Github user manishamde commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-36755664
Thanks Sean.
Multi-class classification and feature importances are important features
that will be added soon. We implemented a minimal feature set since we wan
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/83#issuecomment-36753175
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/83#issuecomment-36753177
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/34#issuecomment-36753067
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13006/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/34#issuecomment-36753065
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 have t
Hi, all
Just for curiosity, I grep the source code in core component yesterday, and
found that there are about 30 configuration parameters being used but
undocumented
I have been reading the source code and writing documents for them, nearly
finished…
But I would like to ask before I made
GitHub user jyotiska opened a pull request:
https://github.com/apache/spark/pull/83
Fixed link for latest pyspark api guide
Fixed link for PySpark API in Python programming guide to the latest
version.
You can merge this pull request into a Git repository by running:
$ git pul
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/34#issuecomment-36747330
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/34#issuecomment-36747331
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36737006
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 have t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36737007
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13005/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36732960
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36732961
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 th
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36729592
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/80#issuecomment-36728450
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 have t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36728452
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13003/
---
If your pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/18#issuecomment-36728451
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 have t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/18#issuecomment-36728453
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13004/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/18#issuecomment-36723654
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/18#issuecomment-36723653
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36723648
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/81#issuecomment-36723643
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 proje
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/82#issuecomment-36723641
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 proje
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36723647
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 have
GitHub user epahomov opened a pull request:
https://github.com/apache/spark/pull/82
[SPARK-1177] Allow SPARK_JAR to be set in system properties
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/epahomov/spark SPARK-1177
Alternativ
GitHub user epahomov opened a pull request:
https://github.com/apache/spark/pull/81
[SPARK-1174] Adding port configuration for HttpFileServer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/epahomov/spark SPARK-1174
Alternativel
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/80
Spark 1165 rdd.intersection in python and java
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ScrapCodes/spark-1 SPARK-1165/RDD.intersection
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-36719653
I'm looking forward to this. I have one question just based on the
description and not reading the code. Why only binary classification? RDF is
inherently amenable to multi-
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-36719546
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 proje
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/75#issuecomment-36719527
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13002/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/76#issuecomment-36719525
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13001/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/76#issuecomment-36719524
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 have t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/75#issuecomment-36719526
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 have t
101 - 191 of 191 matches
Mail list logo
