Re: Apache Spark 3.2.4 EOL Release?

+1 Hyukjin Kwon 于2023年4月4日 周二下午5:31写道： > +1 > > On Wed, 5 Apr 2023 at 07:31, Mridul Muralidharan wrote: > >> >> +1 >> Sounds good to me. >> >> Thanks, >> Mridul >> >> >> On Tue, Apr 4, 2023 at 1:39 PM huaxin gao wrote: >> >>> +1 >>> >>> On Tue, Apr 4, 2023 at 11:17 AM Chao Sun wrote: >>>

Re: Apache Spark 3.2.4 EOL Release?

+1 On Wed, 5 Apr 2023 at 07:31, Mridul Muralidharan wrote: > > +1 > Sounds good to me. > > Thanks, > Mridul > > > On Tue, Apr 4, 2023 at 1:39 PM huaxin gao wrote: > >> +1 >> >> On Tue, Apr 4, 2023 at 11:17 AM Chao Sun wrote: >> >>> +1 >>> >>> On Tue, Apr 4, 2023 at 11:12 AM Holden Karau >>>

Re: Apache Spark 3.2.4 EOL Release?

+1 Sounds good to me. Thanks, Mridul On Tue, Apr 4, 2023 at 1:39 PM huaxin gao wrote: > +1 > > On Tue, Apr 4, 2023 at 11:17 AM Chao Sun wrote: > >> +1 >> >> On Tue, Apr 4, 2023 at 11:12 AM Holden Karau >> wrote: >> >>> +1 >>> >>> On Tue, Apr 4, 2023 at 11:04 AM L. C. Hsieh wrote: >>>

Re: Apache Spark 3.2.4 EOL Release?

+1 On Tue, Apr 4, 2023 at 11:17 AM Chao Sun wrote: > +1 > > On Tue, Apr 4, 2023 at 11:12 AM Holden Karau wrote: > >> +1 >> >> On Tue, Apr 4, 2023 at 11:04 AM L. C. Hsieh wrote: >> >>> +1 >>> >>> Sounds good and thanks Dongjoon for driving this. >>> >>> On 2023/04/04 17:24:54 Dongjoon Hyun

Re: Apache Spark 3.2.4 EOL Release?

+1 On Tue, Apr 4, 2023 at 11:12 AM Holden Karau wrote: > +1 > > On Tue, Apr 4, 2023 at 11:04 AM L. C. Hsieh wrote: > >> +1 >> >> Sounds good and thanks Dongjoon for driving this. >> >> On 2023/04/04 17:24:54 Dongjoon Hyun wrote: >> > Hi, All. >> > >> > Since Apache Spark 3.2.0 passed RC7 vote

Re: Apache Spark 3.2.4 EOL Release?

+1 On Tue, Apr 4, 2023 at 11:04 AM L. C. Hsieh wrote: > +1 > > Sounds good and thanks Dongjoon for driving this. > > On 2023/04/04 17:24:54 Dongjoon Hyun wrote: > > Hi, All. > > > > Since Apache Spark 3.2.0 passed RC7 vote on October 12, 2021, branch-3.2 > > has been maintained and served well

Re: Apache Spark 3.2.4 EOL Release?

+1 Sounds good and thanks Dongjoon for driving this. On 2023/04/04 17:24:54 Dongjoon Hyun wrote: > Hi, All. > > Since Apache Spark 3.2.0 passed RC7 vote on October 12, 2021, branch-3.2 > has been maintained and served well until now. > > - https://github.com/apache/spark/releases/tag/v3.2.0

Apache Spark 3.2.4 EOL Release?

Hi, All. Since Apache Spark 3.2.0 passed RC7 vote on October 12, 2021, branch-3.2 has been maintained and served well until now. - https://github.com/apache/spark/releases/tag/v3.2.0 (tagged on Oct 6, 2021) - https://lists.apache.org/thread/jslhkh9sb5czvdsn7nz4t40xoyvznlc7 As of today,

Release Note of Apache Spark 3.4.0

Hi All, Thank you all for your valuable contributions to the Spark 3.4 release so far! I would appreciate your review and feedback on the release note. Please see here for the draft

Re: [VOTE] Release Apache Spark 3.4.0 (RC5)

Thank you Wenchen for the report. I marked them as blockers just now. On Tue, Apr 4, 2023 at 10:52 AM Wenchen Fan wrote: > Sorry for the last-minute change, but we found two wrong behaviors and > want to fix them before the release: > > https://github.com/apache/spark/pull/40641 > We missed a

Re: Slack for PySpark users

That 3 months retention is just a soft setting. For low volume traffic, it can be negotiated to a year’s retention. Let me see what we can do about it. HTH On Tue, 4 Apr 2023 at 09:31, Bjørn Jørgensen wrote: > One of the things that I don't like about this slack solution is that > questions

Re: Slack for PySpark users

One of the things that I don't like about this slack solution is that questions and answers disappear after 90 days. Today's maillist solution is indexed by search engines and when one day you wonder about something, you can find solutions with the help of just searching the web. Another question

Re: Slack for PySpark users

Hi Shani, I believe I am an admin so that is fine by me. Hi Dongioon, With regard to summarising the discussion etc, no need, It is like flogging the dead horse, we have already discussed it enough. I don't see the point of it. HTH Mich Talebzadeh, Lead Solutions Architect/Engineering Lead