Congrats!!
--
Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/
-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
Congrats, all!
Bests,
Takeshi
On Fri, Jun 19, 2020 at 1:16 PM Felix Cheung
wrote:
> Congrats
>
> --
> *From:* Jungtaek Lim
> *Sent:* Thursday, June 18, 2020 8:18:54 PM
> *To:* Hyukjin Kwon
> *Cc:* Mridul Muralidharan ; Reynold Xin <
> r...@databricks.com>; dev ;
CELEBRATIONS!!!
On Thu, Jun 18, 2020 at 6:21 PM Reynold Xin wrote:
> Hi all,
>
> Apache Spark 3.0.0 is the first release of the 3.x line. It builds on many
> of the innovations from Spark 2.x, bringing new ideas as well as continuing
> long-term projects that have been in development.
Hi all
I've upgraded my test cluster to spark 3 and change my comitter to
directory and I still get this error.. The documentations are somehow
obscure on that.
Do I need to add a third party jar to support new comitters?
java.lang.ClassNotFoundException:
Congrats
From: Jungtaek Lim
Sent: Thursday, June 18, 2020 8:18:54 PM
To: Hyukjin Kwon
Cc: Mridul Muralidharan ; Reynold Xin ;
dev ; user
Subject: Re: [ANNOUNCE] Apache Spark 3.0.0
Great, thanks all for your efforts on the huge step forward!
On Fri, Jun 19,
Great, thanks all for your efforts on the huge step forward!
On Fri, Jun 19, 2020 at 12:13 PM Hyukjin Kwon wrote:
> Yay!
>
> 2020년 6월 19일 (금) 오전 4:46, Mridul Muralidharan 님이 작성:
>
>> Great job everyone ! Congratulations :-)
>>
>> Regards,
>> Mridul
>>
>> On Thu, Jun 18, 2020 at 10:21 AM Reynold
Yay!
2020년 6월 19일 (금) 오전 4:46, Mridul Muralidharan 님이 작성:
> Great job everyone ! Congratulations :-)
>
> Regards,
> Mridul
>
> On Thu, Jun 18, 2020 at 10:21 AM Reynold Xin wrote:
>
>> Hi all,
>>
>> Apache Spark 3.0.0 is the first release of the 3.x line. It builds on
>> many of the innovations
Second paragraph of the PR lists the design doc.
> There is a design document at
https://docs.google.com/document/d/1xVO1b6KAwdUhjEJBolVPl9C6sLj7oOveErwDSYdT-pE/edit?usp=sharing
On Thu, 18 Jun 2020 at 18:05, Hyukjin Kwon wrote:
> Looks it had to be with SPIP and a proper design doc to discuss.
For follow up while I've backported this in some internal releases I'm not
considering a candidate for backporting to Spark 3 anymore. I should have
updated the thread with that. The design doc is linked in the PR.
On Thu, Jun 18, 2020 at 6:05 PM Hyukjin Kwon wrote:
> Looks it had to be with
Looks it had to be with SPIP and a proper design doc to discuss.
2020년 2월 9일 (일) 오전 1:23, Erik Erlandson 님이 작성:
> I'd be willing to pull this in, unless others have concerns post
> branch-cut.
>
> On Tue, Feb 4, 2020 at 2:51 PM Holden Karau wrote:
>
>> Hi Y’all,
>>
>> I’ve got a K8s graceful
I really dislike the use of "worker" in the code base since it describes a
process which doesn't actually do work, but I don't think it's in the scope
for this ticket. I would definitely prefer we use "agent" instead of
"worker" (or some other name) and have master switched to something like
Thanks a lot for proposing this, Holden.
I'd be curious to know how others feel about also tackling the word
blacklist -- while I think most would agree it is not as egregious as
master/slave, it seems to be an appropriate time to use the momentum to
really a make a best effort at removing any
So I think using Worker everywhere would be a bit confusing since the
relationship between worker and blockmanager replica is complex, also in
the current PR `AgentLost` is not `WorkerLost` because it doesn't
necessarily mean the worker is lost (there's a flag for if the worker has
been lost).
On
Yup, it would be great to do this. FWIW, I would propose using “worker”
everywhere instead unless it already means something in that context, just to
have a single word for this (instead of multiple words such as agent, replica,
etc), but I haven’t looked into whether that would make anything
Thank you. I agree being careful with API comparability is important. I
think in situations where the terms are exposed in our API we can introduce
alternatives and deprecate the old ones to allow for a smooth migration.
On Thu, Jun 18, 2020 at 12:28 PM Reynold Xin wrote:
> Thanks for doing
Great job everyone ! Congratulations :-)
Regards,
Mridul
On Thu, Jun 18, 2020 at 10:21 AM Reynold Xin wrote:
> Hi all,
>
> Apache Spark 3.0.0 is the first release of the 3.x line. It builds on many
> of the innovations from Spark 2.x, bringing new ideas as well as continuing
> long-term
Thanks for doing this. I think this is a great thing to do.
But we gotta be careful with API compatibility.
On Thu, Jun 18, 2020 at 11:32 AM, Holden Karau < hol...@pigscanfly.ca > wrote:
>
> Hi Folks,
>
>
> I've started working on cleaning up the Spark code to remove references to
> slave
Congratulations 拾
Celebrating 拾
Sent from my iPhone
> On 18 Jun 2020, at 20:38, Gourav Sengupta wrote:
>
>
> CELEBRATIONS!!!
>
>> On Thu, Jun 18, 2020 at 6:21 PM Reynold Xin wrote:
>> Hi all,
>>
>> Apache Spark 3.0.0 is the first release of the 3.x line. It builds on many
>> of
Hi Folks,
I've started working on cleaning up the Spark code to remove references to
slave since the word has a lot of negative connotations and we can
generally replace it with more accurate/descriptive words in our code base.
The PR is at https://github.com/apache/spark/pull/28864 (I'm a little
Hi all,
Apache Spark 3.0.0 is the first release of the 3.x line. It builds on many of
the innovations from Spark 2.x, bringing new ideas as well as continuing
long-term projects that have been in development. This release resolves more
than 3400 tickets.
We'd like to thank our contributors
20 matches
Mail list logo
