+1
Tested SparkR package manually on multiple platforms and checked different
Hadoop release jar.
And previously tested the last RC on different R releases (see the last RC vote
thread)
I found some differences in bin release jars created by the different options
when running the
Hmm, sounds like some sort of corruption of the maven directory on the Jenkins
box...
From: Liwei Lin
Sent: Wednesday, October 4, 2017 6:52:54 PM
To: Spark dev list
Subject: Nightly builds for master branch failed
To be sure, this is only for JIRA and not for github PR, right?
If then +1 but I think the access control on JIRA does not necessarily match
the committer list, and is manually maintained, last I hear.
From: Sean Owen
Sent: Wednesday,
Although I assume we could get an account suspended if it started opening
spam issues, yes we default to letting anyone open issues, and potentially
abusing it. That much is the right default and I don't see any policy tweak
that stops that.
I see several INFRA tickets asking to *allow* the
It can stop reopening, but new JIRA issues with duplicate content will be
created intentionally instead.
Is that policy (privileged reopening) used in other Apache communities for
that purpose?
On Wed, Oct 4, 2017 at 7:06 PM, Sean Owen wrote:
> We have this problem
We have this problem occasionally, where a disgruntled user continually
reopens an issue after it's closed.
https://issues.apache.org/jira/browse/SPARK-21999
(Feel free to comment on this one if anyone disagrees)
Regardless of that particular JIRA, I'd like to disable to Closed ->
Reopened
Congratulations!
Cheers,
Liwei
On Wed, Oct 4, 2017 at 2:27 PM, Yuval Itzchakov wrote:
> Congratulations and Good luck! :)
>
>
>
> --
> Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/
>
>
https://amplab.cs.berkeley.edu/jenkins/job/spark-master-maven-snapshots/
Nightly builds for master branch failed due to:
[error] error: error reading
/home/jenkins/.m2/repository/com/fasterxml/jackson/core/jackson-databind/
2.6.7.1/jackson-databind-2.6.7.1.jar; zip file is empty
Can we get it
+1 (non-binding)
Cheers,
Liwei
On Wed, Oct 4, 2017 at 4:03 PM, Nick Pentreath
wrote:
> Ah right! Was using a new cloud instance and didn't realize I was logged
> in as root! thanks
>
> On Tue, 3 Oct 2017 at 21:13 Marcelo Vanzin wrote:
>
>> Maybe
Kumar,
This is a good start: http://spark.apache.org/contributing.html
On Wed, Oct 4, 2017 at 10:00 AM, vaquar khan wrote:
> Hi Nishant,
>
> 1) Start with helping spark users on mailing list and stack .
>
> 2) Start helping build and testing.
>
> 3) Once comfortable
Hi Nishant,
1) Start with helping spark users on mailing list and stack .
2) Start helping build and testing.
3) Once comfortable with code start working on Spark Jira.
Regards,
Vaquar khan
On Oct 4, 2017 11:29 AM, "Kumar Nishant" wrote:
> Hi Team,
> I am new to
Hi Team,
I am new to Apache community and I would love to contribute effort in Spark
development. Can anyone mentor & guide me how to proceed and start
contributing? I am beginner here so I am not sure what process is be
followed.
Thanks
Nishant
Ah right! Was using a new cloud instance and didn't realize I was logged in
as root! thanks
On Tue, 3 Oct 2017 at 21:13 Marcelo Vanzin wrote:
> Maybe you're running as root (or the admin account on your OS)?
>
> On Tue, Oct 3, 2017 at 12:12 PM, Nick Pentreath
>
Congratulations and Good luck! :)
--
Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/
-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
14 matches
Mail list logo