+1
On Tue, Feb 11, 2014 at 9:17 AM, Matt Massie mas...@berkeley.edu wrote:
+1
--
Matt Massie
UC, Berkeley AMPLab
Twitter: @matt_massie https://twitter.com/matt_massie,
@amplabhttps://twitter.com/amplab
https://amplab.cs.berkeley.edu/
On Mon, Feb 10, 2014 at 11:12 PM, Zongheng Yang
+1 (binding)
On 02/11/2014 09:02 AM, Nick Pentreath wrote:
+1
On Tue, Feb 11, 2014 at 9:17 AM, Matt Massie mas...@berkeley.edu wrote:
+1
--
Matt Massie
UC, Berkeley AMPLab
Twitter: @matt_massie https://twitter.com/matt_massie,
@amplabhttps://twitter.com/amplab
Github user NirmalReddy commented on the pull request:
https://github.com/apache/incubator-spark/pull/475#issuecomment-34736734
@tdas Can you please verify this patch. Thanks !!
GitHub user jyotiska opened a pull request:
https://github.com/apache/incubator-spark/pull/581
Added extra description on ValueError when one Spark context already exists
I added extra description on the ValueError message, when more than one
Spark context already exists. Added the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/581#issuecomment-34758328
Can one of the admins verify this patch?
Github user jyotiska closed the pull request at:
https://github.com/apache/incubator-spark/pull/581
GitHub user jyotiska reopened a pull request:
https://github.com/apache/incubator-spark/pull/581
Added extra description on ValueError when one Spark context already exists
I added extra description on the ValueError message, when more than one
Spark context already exists. Added
+1
On Mon, Feb 10, 2014 at 8:27 PM, Chris Mattmann mattm...@apache.org wrote:
Hi Everyone,
This is a new VOTE to decide if Apache Spark should graduate
from the Incubator. Please VOTE on the resolution pasted below
the ballot. I'll leave this VOTE open for at least 72 hours.
Thanks!
[
+1 !
- Mridul
On Tue, Feb 11, 2014 at 9:57 AM, Chris Mattmann mattm...@apache.org wrote:
Hi Everyone,
This is a new VOTE to decide if Apache Spark should graduate
from the Incubator. Please VOTE on the resolution pasted below
the ballot. I'll leave this VOTE open for at least 72 hours.
Github user tgravescs commented on the pull request:
https://github.com/apache/incubator-spark/pull/332#issuecomment-34763698
Sorry for my delay, I was on vacation last week. Thanks for the reviews,
I'll go through them and respond.
It sounds like you want 2 types of
+1
+1
--
GIRI IYENGAR, CTO
VELOS.IO
Simple. Powerful. Predictions.
440 NINTH AVE, 11TH FLOOR NEW YORK CITY, NY 10001
O: 917.525.2466x104 M: 914.924.7935
E: *giri.iyengar@v giri.iyen...@sociocast.comelos.io
http://elos.io* W: *www.velos.
http://www.sociocast.com/io*
+1
Yours, Xuefeng Wu 吴雪峰 敬上
On 2014年2月11日, at 下午12:27, Chris Mattmann mattm...@apache.org wrote:
Hi Everyone,
This is a new VOTE to decide if Apache Spark should graduate
from the Incubator. Please VOTE on the resolution pasted below
the ballot. I'll leave this VOTE open for at least
+1 !!!
On 2/10/14, 9:27 PM, Chris Mattmann mattm...@apache.org wrote:
Hi Everyone,
This is a new VOTE to decide if Apache Spark should graduate
from the Incubator. Please VOTE on the resolution pasted below
the ballot. I'll leave this VOTE open for at least 72 hours.
Thanks!
[ ] +1 Graduate
+1.
Tom
On Tuesday, February 11, 2014 10:13 AM, Andrew Psaltis
psaltis.and...@gmail.com wrote:
+1
On Tue, Feb 11, 2014 at 8:50 AM, Giri Iyengar giri.iyen...@velos.io wrote:
+1
--
GIRI IYENGAR, CTO
VELOS.IO
Simple. Powerful. Predictions.
440 NINTH AVE, 11TH FLOOR NEW YORK CITY,
+1
This is a bit aside, but are we also getting jenkins machine in the apache
domain?
Tom
On Friday, February 7, 2014 1:54 AM, Kostas Sakellis kos...@cloudera.com
wrote:
+1
On Thursday, February 6, 2014, Sandy Ryza sandy.r...@cloudera.com wrote:
+1
On Thu, Feb 6, 2014 at 4:10 PM,
+1
--
View this message in context:
http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Graduation-of-Apache-Spark-from-the-Incubator-tp1022p1082.html
Sent from the Apache Spark Developers List mailing list archive at Nabble.com.
+1
Craig
On Feb 10, 2014, at 8:27 PM, Chris Mattmann wrote:
Hi Everyone,
This is a new VOTE to decide if Apache Spark should graduate
from the Incubator. Please VOTE on the resolution pasted below
the ballot. I'll leave this VOTE open for at least 72 hours.
Thanks!
[ ] +1 Graduate
+ 1 (binding).
Suresh
On Feb 10, 2014, at 11:27 PM, Chris Mattmann mattm...@apache.org wrote:
Hi Everyone,
This is a new VOTE to decide if Apache Spark should graduate
from the Incubator. Please VOTE on the resolution pasted below
the ballot. I'll leave this VOTE open for at least 72
Github user jyotiska commented on the pull request:
https://github.com/apache/incubator-spark/pull/581#issuecomment-34782466
This tries to solve
[SPARK-972](https://spark-project.atlassian.net/browse/SPARK-972)
On Mon, Feb 10, 2014 at 8:27 PM, Chris Mattmann mattm...@apache.org wrote:
[ ] +1 Graduate Apache Spark from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Spark from the Incubator because..
+1 (binding)
Marvin Humphrey
The ASF infra support all Hadoop and it's community projects CI requests,
as well as other ASF projects.
From my experience with other ASF projects the Jenkins support has been
great.
And also ASF infra is accepting help if you guys think you could spare time
and knowledge.
Henry
On Tuesday,
+1 to the proposal
On Thursday, February 6, 2014, Patrick Wendell pwend...@gmail.com wrote:
As a break out from the other thread. I'd like to propose two
guidelines for pull requests. These guidelines are to make things
easier to track for developers and users, and to help organize the
large
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34792614
Merged build triggered.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34792615
Merged build started.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34792737
Merged build finished.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34792740
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12677/
+1 (binding)
-Jake
On Mon, Feb 10, 2014 at 11:27 PM, Chris Mattmann mattm...@apache.orgwrote:
Hi Everyone,
This is a new VOTE to decide if Apache Spark should graduate
from the Incubator. Please VOTE on the resolution pasted below
the ballot. I'll leave this VOTE open for at least 72
On Mon, Feb 10, 2014 at 8:27 PM, Chris Mattmann mattm...@apache.org wrote:
Hi Everyone,
This is a new VOTE to decide if Apache Spark should graduate
from the Incubator. Please VOTE on the resolution pasted below
the ballot. I'll leave this VOTE open for at least 72 hours.
Thanks!
[ ] +1
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34795845
Merged build triggered.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34797009
Merged build started.
Github user jyotiska commented on the pull request:
https://github.com/apache/incubator-spark/pull/581#issuecomment-34796972
I understand. Maybe we can use a global variable to store the call site
(line number?) and print it back along with the address. What do you think?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34797008
Merged build triggered.
Github user JoshRosen commented on the pull request:
https://github.com/apache/incubator-spark/pull/581#issuecomment-34797494
I'd store the constructor's call site (filename + line number) as an
instance variable inside SparkContext, since we already have the
Github user jyotiska commented on the pull request:
https://github.com/apache/incubator-spark/pull/581#issuecomment-34798126
Got it. I will work on it and report it back to you. I guess traceback
module will be useful here.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34798894
Merged build finished.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34798895
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12678/
Github user JoshRosen commented on the pull request:
https://github.com/apache/incubator-spark/pull/581#issuecomment-34799232
You may be able to re-use the
[`_extract_concise_traceback`](https://github.com/apache/incubator-spark/pull/311/files#diff-d6fe2792e44f6babc94aabfefc8b9bceR43)
GitHub user willb opened a pull request:
https://github.com/apache/incubator-spark/pull/582
SPARK-1078: Replace lift-json with json4s-jackson.
The aim of the Json4s project is to provide a common API for
Scala JSON libraries. It is Apache-licensed, easier for
downstream
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/582#issuecomment-34799861
Can one of the admins verify this patch?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34800114
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12679/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#issuecomment-34800110
Merged build finished.
Github user rxin commented on the pull request:
https://github.com/apache/incubator-spark/pull/582#issuecomment-34801246
Jenkins, add to whitelist.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/582#issuecomment-34801415
Merged build triggered.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/582#issuecomment-34801416
Merged build started.
Github user jyotiska commented on the pull request:
https://github.com/apache/incubator-spark/pull/581#issuecomment-34804481
I have used the _extract_concise_traceback to print the callsite of
existing SparkContext. I guess this is what you had in mind.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/582#issuecomment-34804702
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12680/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/582#issuecomment-34804701
Merged build finished.
Github user rxin commented on the pull request:
https://github.com/apache/incubator-spark/pull/577#issuecomment-34817976
Thanks. I've merged this.
Github user rxin commented on the pull request:
https://github.com/apache/incubator-spark/pull/571#issuecomment-34818238
Thanks. I've merged this.
Hi Guys,
With ASF JIRA still in transfer mode, could someone with permission to
add my userid hsaputra in https://spark-project.atlassian.net so I
could assign issues and resolve them myself?
CC @pwendell or @rxin
Thanks,
- Henry
Thanks Reynold! =)
- Henry
On Tue, Feb 11, 2014 at 3:05 PM, Reynold Xin r...@databricks.com wrote:
I added you to the dev list on jira for spark.
On Tue, Feb 11, 2014 at 2:58 PM, Henry Saputra henry.sapu...@gmail.comwrote:
Hi Guys,
With ASF JIRA still in transfer mode, could someone with
Github user hsaputra closed the pull request at:
https://github.com/apache/incubator-spark/pull/577
+1 (non-binding)
On Tue, Feb 11, 2014 at 8:31 AM, Sean McNamara
sean.mcnam...@webtrends.comwrote:
+1 !!!
On 2/10/14, 9:27 PM, Chris Mattmann mattm...@apache.org wrote:
Hi Everyone,
This is a new VOTE to decide if Apache Spark should graduate
from the Incubator. Please VOTE on the
Github user liancheng commented on the pull request:
https://github.com/apache/incubator-spark/pull/571#issuecomment-34825349
@aarondav I wonder is `@specialized` can be used here to avoid the type
dispatching in `CollectionUtils`?
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/582#issuecomment-34829822
Does json4s-jackson include any dependencies that lift-json doesn't? Does
the versioning match?
It seems that this version of json4s-jackson pulls in
Github user colorant commented on the pull request:
https://github.com/apache/incubator-spark/pull/553#issuecomment-34830448
@sryza I think this depends on what you mean to do with the yarn-client
mode, for spark-shell, since it is already packaged in the assembly jar. you
don't need
Github user sryza commented on the pull request:
https://github.com/apache/incubator-spark/pull/553#issuecomment-34830852
It's true that you may need it when running in yarn-client mode. And also
true that you will not when running spark-shell. Because it depends, I think
not
Github user colorant commented on the pull request:
https://github.com/apache/incubator-spark/pull/553#issuecomment-34831254
I agree that we do not need a hard check on it :) This patch looks good to
me, I just wonder we might need a few more explanation to clarify why this one
is
Should be fixed in both alpha and stable code base, since we aim to support
both version
Best Regards,
Raymond Liu
-Original Message-
From: Nan Zhu [mailto:zhunanmcg...@gmail.com]
Sent: Wednesday, February 12, 2014 10:29 AM
To: dev@spark.incubator.apache.org
Subject: Does yarn-stable
Github user willb commented on the pull request:
https://github.com/apache/incubator-spark/pull/582#issuecomment-34834423
The current version of json4s-jackson depends on paranamer 2.6, while the
current version of lift-json depends on 2.4.1. That's the only difference that
winds up
I am not sure I fully understand this reasoning. I imagine that lift-json
is only one of hundreds of packages that would have to be built if you
wanted to build all of Spark's transitive dependencies from source.
Additionally, to make sure I understand the impact -- this is only intended
to
Github user jyotiska commented on the pull request:
https://github.com/apache/incubator-spark/pull/581#issuecomment-34836413
I think for future improvements, it would be a good idea to move the
traceback code to a separate file and use that to return callsite. Please start
a JIRA
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/582#issuecomment-34836430
Thanks for looking into it! The situation sounds fine for the next minor
release, and I don't think this patch needs to be included in the next
maintenance
I think Aaron just meant 1.0.0 by the next minor release.
On Tue, Feb 11, 2014 at 7:56 PM, Mark Hamstra m...@clearstorydata.com wrote:
The situation sounds fine for the next minor release...
I don't understand what you mean by this. According to my current
understanding, the next release
GitHub user colorant opened a pull request:
https://github.com/apache/incubator-spark/pull/583
Minor fix for ZooKeeperPersistenceEngine to use configured working dir
You can merge this pull request into a Git repository by running:
$ git pull
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/583#issuecomment-34838201
Good catch! LGTM.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/583#issuecomment-34838194
Merged build started.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/583#issuecomment-34838371
Merged build triggered.
Github user colorant commented on the pull request:
https://github.com/apache/incubator-spark/pull/583#issuecomment-34838369
oops, catch me ;) updated
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/583#issuecomment-34838372
Merged build started.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/583#issuecomment-34838606
Merged build triggered.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/583#issuecomment-34838607
Merged build started.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/522#issuecomment-34839013
Build started.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/522#issuecomment-34839050
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12684/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/522#issuecomment-34839049
Build finished.
Github user pwendell commented on the pull request:
https://github.com/apache/incubator-spark/pull/522#issuecomment-34839244
@bijaybisht this is out of date with master - mind bringing it up to date?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/583#issuecomment-34839331
Merged build finished.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/583#issuecomment-34839550
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12682/
Github user bijaybisht closed the pull request at:
https://github.com/apache/incubator-spark/pull/522
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/584#issuecomment-34841291
Can one of the admins verify this patch?
Github user bijaybisht commented on the pull request:
https://github.com/apache/incubator-spark/pull/522#issuecomment-34841425
Pls merge #584 which is merge able now.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/578#issuecomment-34842337
Merged build started.
Github user mengxr commented on the pull request:
https://github.com/apache/incubator-spark/pull/578#issuecomment-34842407
@rxin Thanks! Please see the updated code.
Sounds good, now that we are all clear on what we mean. Didn't mean to be
a dick, just was a little confused on what you meant.
On Tue, Feb 11, 2014 at 8:08 PM, Patrick Wendell pwend...@gmail.com wrote:
I think Aaron just meant 1.0.0 by the next minor release.
On Tue, Feb 11, 2014 at 7:56
Github user pwendell commented on the pull request:
https://github.com/apache/incubator-spark/pull/584#issuecomment-34843361
Jenkins, test this please.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/584#issuecomment-34843445
Merged build started.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/584#issuecomment-34843473
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12686/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/578#issuecomment-34843553
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12685/
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/583#issuecomment-34843731
Merged into master and cherry-picked into branch-0.9 and branch-0.8.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/584#issuecomment-34844919
Merged build started.
Github user rxin commented on the pull request:
https://github.com/apache/incubator-spark/pull/584#issuecomment-34844932
It's because branch-0.9 doesn't have the scalastyle stuff ...
Github user rxin commented on the pull request:
https://github.com/apache/incubator-spark/pull/584#issuecomment-34844952
BTW Jenkins desire assertiveness. By asking him whether you could do this,
he wouldn't do it ...
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/584#issuecomment-34845592
Jenkins, retest this please.
94 matches
Mail list logo
