Re: Apache Spark 3.2.4 EOL Release?

2023-04-04 Thread Yuming Wang 
+1

On Wed, Apr 5, 2023 at 9:09 AM Xinrong Meng 
wrote:

> +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:

> +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 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, branch-3.2 has 62 additional patches after v3.2.3 and
>>> reaches
>>> > the end-of-life this month according to the Apache Spark release
>>> cadence. (
>>> > https://spark.apache.org/versioning-policy.html)
>>> >
>>> > $ git log --oneline v3.2.3..HEAD | wc -l
>>> > 62
>>> >
>>> > With the upcoming Apache Spark 3.4, I hope the users can get a
>>> chance to
>>> > have these last bits of Apache Spark 3.2.x, and I'd like to
>>> propose to have
>>> > Apache Spark 3.2.4 EOL Release next week and volunteer as the
>>> release
>>> > manager. WDTY? Please let me know if you need more patches on
>>> branch-3.2.
>>> >
>>> > Thanks,
>>> > Dongjoon.
>>> >
>>>
>>> -
>>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>>
>>> --
>> Twitter: https://twitter.com/holdenkarau
>> Books (Learning Spark, High Performance Spark, etc.):
>> https://amzn.to/2MaRAG9  
>> YouTube Live Streams: https://www.youtube.com/user/holdenkarau
>>
>

Re: Apache Spark 3.2.4 EOL Release?

2023-04-04 Thread Xinrong Meng 
+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:
>>>
 +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 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, branch-3.2 has 62 additional patches after v3.2.3 and
>> reaches
>> > the end-of-life this month according to the Apache Spark release
>> cadence. (
>> > https://spark.apache.org/versioning-policy.html)
>> >
>> > $ git log --oneline v3.2.3..HEAD | wc -l
>> > 62
>> >
>> > With the upcoming Apache Spark 3.4, I hope the users can get a
>> chance to
>> > have these last bits of Apache Spark 3.2.x, and I'd like to propose
>> to have
>> > Apache Spark 3.2.4 EOL Release next week and volunteer as the
>> release
>> > manager. WDTY? Please let me know if you need more patches on
>> branch-3.2.
>> >
>> > Thanks,
>> > Dongjoon.
>> >
>>
>> -
>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>
>> --
> Twitter: https://twitter.com/holdenkarau
> Books (Learning Spark, High Performance Spark, etc.):
> https://amzn.to/2MaRAG9  
> YouTube Live Streams: https://www.youtube.com/user/holdenkarau
>

Re: Apache Spark 3.2.4 EOL Release?

2023-04-04 Thread Hyukjin Kwon 
+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 
>>> 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 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, branch-3.2 has 62 additional patches after v3.2.3 and
> reaches
> > the end-of-life this month according to the Apache Spark release
> cadence. (
> > https://spark.apache.org/versioning-policy.html)
> >
> > $ git log --oneline v3.2.3..HEAD | wc -l
> > 62
> >
> > With the upcoming Apache Spark 3.4, I hope the users can get a
> chance to
> > have these last bits of Apache Spark 3.2.x, and I'd like to propose
> to have
> > Apache Spark 3.2.4 EOL Release next week and volunteer as the release
> > manager. WDTY? Please let me know if you need more patches on
> branch-3.2.
> >
> > Thanks,
> > Dongjoon.
> >
>
> -
> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>
> --
 Twitter: https://twitter.com/holdenkarau
 Books (Learning Spark, High Performance Spark, etc.):
 https://amzn.to/2MaRAG9  
 YouTube Live Streams: https://www.youtube.com/user/holdenkarau

>>>

Re: Apache Spark 3.2.4 EOL Release?

2023-04-04 Thread Mridul Muralidharan 
+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:
>>>
 +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 (tagged on Oct
 6,
 > 2021)
 > - https://lists.apache.org/thread/jslhkh9sb5czvdsn7nz4t40xoyvznlc7
 >
 > As of today, branch-3.2 has 62 additional patches after v3.2.3 and
 reaches
 > the end-of-life this month according to the Apache Spark release
 cadence. (
 > https://spark.apache.org/versioning-policy.html)
 >
 > $ git log --oneline v3.2.3..HEAD | wc -l
 > 62
 >
 > With the upcoming Apache Spark 3.4, I hope the users can get a chance
 to
 > have these last bits of Apache Spark 3.2.x, and I'd like to propose
 to have
 > Apache Spark 3.2.4 EOL Release next week and volunteer as the release
 > manager. WDTY? Please let me know if you need more patches on
 branch-3.2.
 >
 > Thanks,
 > Dongjoon.
 >

 -
 To unsubscribe e-mail: dev-unsubscr...@spark.apache.org

 --
>>> Twitter: https://twitter.com/holdenkarau
>>> Books (Learning Spark, High Performance Spark, etc.):
>>> https://amzn.to/2MaRAG9  
>>> YouTube Live Streams: https://www.youtube.com/user/holdenkarau
>>>
>>

Re: Apache Spark 3.2.4 EOL Release?

2023-04-04 Thread huaxin gao 
+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 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 (tagged on Oct
>>> 6,
>>> > 2021)
>>> > - https://lists.apache.org/thread/jslhkh9sb5czvdsn7nz4t40xoyvznlc7
>>> >
>>> > As of today, branch-3.2 has 62 additional patches after v3.2.3 and
>>> reaches
>>> > the end-of-life this month according to the Apache Spark release
>>> cadence. (
>>> > https://spark.apache.org/versioning-policy.html)
>>> >
>>> > $ git log --oneline v3.2.3..HEAD | wc -l
>>> > 62
>>> >
>>> > With the upcoming Apache Spark 3.4, I hope the users can get a chance
>>> to
>>> > have these last bits of Apache Spark 3.2.x, and I'd like to propose to
>>> have
>>> > Apache Spark 3.2.4 EOL Release next week and volunteer as the release
>>> > manager. WDTY? Please let me know if you need more patches on
>>> branch-3.2.
>>> >
>>> > Thanks,
>>> > Dongjoon.
>>> >
>>>
>>> -
>>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>>
>>> --
>> Twitter: https://twitter.com/holdenkarau
>> Books (Learning Spark, High Performance Spark, etc.):
>> https://amzn.to/2MaRAG9  
>> YouTube Live Streams: https://www.youtube.com/user/holdenkarau
>>
>

Re: Apache Spark 3.2.4 EOL Release?

2023-04-04 Thread Chao Sun 
+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 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, branch-3.2 has 62 additional patches after v3.2.3 and
>> reaches
>> > the end-of-life this month according to the Apache Spark release
>> cadence. (
>> > https://spark.apache.org/versioning-policy.html)
>> >
>> > $ git log --oneline v3.2.3..HEAD | wc -l
>> > 62
>> >
>> > With the upcoming Apache Spark 3.4, I hope the users can get a chance to
>> > have these last bits of Apache Spark 3.2.x, and I'd like to propose to
>> have
>> > Apache Spark 3.2.4 EOL Release next week and volunteer as the release
>> > manager. WDTY? Please let me know if you need more patches on
>> branch-3.2.
>> >
>> > Thanks,
>> > Dongjoon.
>> >
>>
>> -
>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>
>> --
> Twitter: https://twitter.com/holdenkarau
> Books (Learning Spark, High Performance Spark, etc.):
> https://amzn.to/2MaRAG9  
> YouTube Live Streams: https://www.youtube.com/user/holdenkarau
>

Re: Apache Spark 3.2.4 EOL Release?

2023-04-04 Thread Holden Karau 
+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 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, branch-3.2 has 62 additional patches after v3.2.3 and
> reaches
> > the end-of-life this month according to the Apache Spark release
> cadence. (
> > https://spark.apache.org/versioning-policy.html)
> >
> > $ git log --oneline v3.2.3..HEAD | wc -l
> > 62
> >
> > With the upcoming Apache Spark 3.4, I hope the users can get a chance to
> > have these last bits of Apache Spark 3.2.x, and I'd like to propose to
> have
> > Apache Spark 3.2.4 EOL Release next week and volunteer as the release
> > manager. WDTY? Please let me know if you need more patches on branch-3.2.
> >
> > Thanks,
> > Dongjoon.
> >
>
> -
> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>
> --
Twitter: https://twitter.com/holdenkarau
Books (Learning Spark, High Performance Spark, etc.):
https://amzn.to/2MaRAG9  
YouTube Live Streams: https://www.youtube.com/user/holdenkarau

Re: Apache Spark 3.2.4 EOL Release?

2023-04-04 Thread L. C. Hsieh 
+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 (tagged on Oct 6,
> 2021)
> - https://lists.apache.org/thread/jslhkh9sb5czvdsn7nz4t40xoyvznlc7
> 
> As of today, branch-3.2 has 62 additional patches after v3.2.3 and reaches
> the end-of-life this month according to the Apache Spark release cadence. (
> https://spark.apache.org/versioning-policy.html)
> 
> $ git log --oneline v3.2.3..HEAD | wc -l
> 62
> 
> With the upcoming Apache Spark 3.4, I hope the users can get a chance to
> have these last bits of Apache Spark 3.2.x, and I'd like to propose to have
> Apache Spark 3.2.4 EOL Release next week and volunteer as the release
> manager. WDTY? Please let me know if you need more patches on branch-3.2.
> 
> Thanks,
> Dongjoon.
> 

-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org

Apache Spark 3.2.4 EOL Release?

2023-04-04 Thread Dongjoon Hyun 
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, branch-3.2 has 62 additional patches after v3.2.3 and reaches
the end-of-life this month according to the Apache Spark release cadence. (
https://spark.apache.org/versioning-policy.html)

$ git log --oneline v3.2.3..HEAD | wc -l
62

With the upcoming Apache Spark 3.4, I hope the users can get a chance to
have these last bits of Apache Spark 3.2.x, and I'd like to propose to have
Apache Spark 3.2.4 EOL Release next week and volunteer as the release
manager. WDTY? Please let me know if you need more patches on branch-3.2.

Thanks,
Dongjoon.

Release Note of Apache Spark 3.4.0

2023-04-04 Thread Xinrong Meng 
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 release note of Apache Spark 3.4.0. Please feel free to add your
comments if any.

Thanks,
Xinrong Meng

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

2023-04-04 Thread Xinrong Meng 
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 corner case when the input index for `array_insert` is 0. It
> should fail as 0 is an invalid index.
>
> https://github.com/apache/spark/pull/40623
> We found some usability issues with a new API and need to change the API
> to fix it. If people have concerns we can also remove the new API entirely.
>
> Thus I'm -1 to this RC. I'll merge these 2 PRs today if no objections.
>
> Thanks,
> Wenchen
>
> On Tue, Apr 4, 2023 at 3:47 AM L. C. Hsieh  wrote:
>
>> +1
>>
>> Thanks Xinrong.
>>
>> On Mon, Apr 3, 2023 at 12:35 PM Dongjoon Hyun 
>> wrote:
>> >
>> > +1
>> >
>> > I also verified that RC5 has SBOM artifacts.
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapachespark-1439/org/apache/spark/spark-core_2.12/3.4.0/spark-core_2.12-3.4.0-cyclonedx.json
>> >
>> https://repository.apache.org/content/repositories/orgapachespark-1439/org/apache/spark/spark-core_2.13/3.4.0/spark-core_2.13-3.4.0-cyclonedx.json
>> >
>> > Thanks,
>> > Dongjoon.
>> >
>> >
>> >
>> > On Mon, Apr 3, 2023 at 1:57 AM yangjie01  wrote:
>> >>
>> >> +1, checked Java 17 + Scala 2.13 + Python 3.10.10.
>> >>
>> >>
>> >>
>> >> 发件人: Herman van Hovell 
>> >> 日期: 2023年3月31日 星期五 12:12
>> >> 收件人: Sean Owen 
>> >> 抄送: Xinrong Meng , dev > >
>> >> 主题: Re: [VOTE] Release Apache Spark 3.4.0 (RC5)
>> >>
>> >>
>> >>
>> >> +1
>> >>
>> >>
>> >>
>> >> On Thu, Mar 30, 2023 at 11:05 PM Sean Owen  wrote:
>> >>
>> >> +1 same result from me as last time.
>> >>
>> >>
>> >>
>> >> On Thu, Mar 30, 2023 at 3:21 AM Xinrong Meng 
>> wrote:
>> >>
>> >> Please vote on releasing the following candidate(RC5) as Apache Spark
>> version 3.4.0.
>> >>
>> >> The vote is open until 11:59pm Pacific time April 4th and passes if a
>> majority +1 PMC votes are cast, with a minimum of 3 +1 votes.
>> >>
>> >> [ ] +1 Release this package as Apache Spark 3.4.0
>> >> [ ] -1 Do not release this package because ...
>> >>
>> >> To learn more about Apache Spark, please see http://spark.apache.org/
>> >>
>> >> The tag to be voted on is v3.4.0-rc5 (commit
>> f39ad617d32a671e120464e4a75986241d72c487):
>> >> https://github.com/apache/spark/tree/v3.4.0-rc5
>> >>
>> >> The release files, including signatures, digests, etc. can be found at:
>> >> https://dist.apache.org/repos/dist/dev/spark/v3.4.0-rc5-bin/
>> >>
>> >> Signatures used for Spark RCs can be found in this file:
>> >> https://dist.apache.org/repos/dist/dev/spark/KEYS
>> >>
>> >> The staging repository for this release can be found at:
>> >> https://repository.apache.org/content/repositories/orgapachespark-1439
>> >>
>> >> The documentation corresponding to this release can be found at:
>> >> https://dist.apache.org/repos/dist/dev/spark/v3.4.0-rc5-docs/
>> >>
>> >> The list of bug fixes going into 3.4.0 can be found at the following
>> URL:
>> >> https://issues.apache.org/jira/projects/SPARK/versions/12351465
>> >>
>> >> This release is using the release script of the tag v3.4.0-rc5.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> FAQ
>> >>
>> >> =
>> >> How can I help test this release?
>> >> =
>> >> If you are a Spark user, you can help us test this release by taking
>> >> an existing Spark workload and running on this release candidate, then
>> >> reporting any regressions.
>> >>
>> >> If you're working in PySpark you can set up a virtual env and install
>> >> the current RC and see if anything important breaks, in the Java/Scala
>> >> you can add the staging repository to your projects resolvers and test
>> >> with the RC (make sure to clean up the artifact cache before/after so
>> >> you don't end up building with an out of date RC going forward).
>> >>
>> >> ===
>> >> What should happen to JIRA tickets still targeting 3.4.0?
>> >> ===
>> >> The current list of open tickets targeted at 3.4.0 can be found at:
>> >> https://issues.apache.org/jira/projects/SPARK and search for "Target
>> Version/s" = 3.4.0
>> >>
>> >> Committers should look at those and triage. Extremely important bug
>> >> fixes, documentation, and API tweaks that impact compatibility should
>> >> be worked on immediately. Everything else please retarget to an
>> >> appropriate release.
>> >>
>> >> ==
>> >> But my bug isn't fixed?
>> >> ==
>> >> In order to make timely releases, we will typically not hold the
>> >> release unless the bug in question is a regression from the previous
>> >> release. That being said, if there is something which is a regression
>> >> that has not been correctly targeted please ping me or a committer to
>> >> help target the issue.
>> >>
>> >>
>> >>
>> >> Thanks,
>> >>
>> >> Xinrong Meng
>> >

Re: Slack for PySpark users

2023-04-04 Thread Mich Talebzadeh 
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 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 that I have is why has apache superset
>  taken away their slack channel. They have
> it linked to on the website but the link is giving errors
> .
> Have they had any experience that this was not the best solution or is it
> just that the link does not work.
>
> tir. 4. apr. 2023 kl. 09:06 skrev Mich Talebzadeh <
> mich.talebza...@gmail.com>:
>
>> 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
>> Palantir Technologies Limited
>>
>>
>>view my Linkedin profile
>> 
>>
>>
>>  https://en.everybodywiki.com/Mich_Talebzadeh
>>
>>
>>
>> *Disclaimer:* Use it at your own risk. Any and all responsibility for
>> any loss, damage or destruction of data or any other property which may
>> arise from relying on this email's technical content is explicitly
>> disclaimed. The author will in no case be liable for any monetary damages
>> arising from such loss, damage or destruction.
>>
>>
>>
>>
>> On Tue, 4 Apr 2023 at 07:06,  wrote:
>>
>>> Hey Dongjoon, Denny and all,
>>>
>>> I’ve created the current slack.
>>> All users have the option to create channels for different topics.
>>>
>>> I don’t see a reason for creating a new one.
>>>
>>> If anyone want to be admin on the current slack channel you all are
>>> welcome to send me a msg and I’ll grand permission.
>>>
>>> Have a great week,
>>> Shani Alisar
>>>
>>>
>>>
>>>
>>>
>>> On 4 Apr 2023, at 3:51, Dongjoon Hyun  wrote:
>>>
>>> 
>>> Thank you, Denny.
>>>
>>> May I interpret your comment as a request to support multiple channels
>>> in ASF too?
>>>
>>> > because it would allow us to create multiple channels for different
>>> topics
>>>
>>> Any other reasons?
>>>
>>> Dongjoon.
>>>
>>>
>>> On Mon, Apr 3, 2023 at 5:31 PM Denny Lee  wrote:
>>>
 I do think creating a new Slack channel would be helpful because it
 would allow us to create multiple channels for different topics -
 streaming, graph, ML, etc.

 We would need a volunteer core to maintain it so we can keep the spirit
 and letter of ASF / code of conduct.  I’d be glad to volunteer to keep this
 active.



 On Mon, Apr 3, 2023 at 16:46 Dongjoon Hyun 
 wrote:

> Shall we summarize the discussion so far?
>
> To sum up, "ASF Slack" vs "3rd-party Slack" was the real background to
> initiate this thread instead of "Slack" vs "Mailing list"?
>
> If ASF Slack provides what you need, is it better than creating a
> new Slack channel?
>
> Or, is there another reason for us to create a new Slack channel?
>
> Dongjoon.
>
>
> On Mon, Apr 3, 2023 at 3:27 PM Mich Talebzadeh <
> mich.talebza...@gmail.com> wrote:
>
>> I agree, whatever individual sentiments are.
>>
>> Mich Talebzadeh,
>> Lead Solutions Architect/Engineering Lead
>> Palantir Technologies Limited
>>
>>
>>view my Linkedin profile
>> 
>>
>>
>>  https://en.everybodywiki.com/Mich_Talebzadeh
>>
>>
>>
>> *Disclaimer:* Use it at your own risk. Any and all responsibility
>> for any loss, damage or destruction of data or any other property which 
>> may
>> arise from relying on this email's technical content is explicitly
>> disclaimed. The author will in no case be liable for any monetary damages
>> arising from such loss, damage or destruction.
>>
>>
>>
>>
>> On Mon, 3 Apr 2023 at 23:21, Jungtaek Lim <
>> kabhwan.opensou...@gmail.com> wrote:
>>
>>> Just to be clear, if there is no strong volunteer to make the new
>>> community channel stay active, I'd probably be OK to not fork the 
>>> channel.
>>> You can see a strong counter example from #spark channel in ASF. It is 
>>> the
>>> place where there are only questions and promos but zero answers. I see
>>> volunteers here demanding for another channel, so I want to see us go 
>>> with
>>> the most preferred way for these vo

Re: Slack for PySpark users

2023-04-04 Thread Bjørn Jørgensen 
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 that I have is why has apache superset
 taken away their slack channel. They have it
linked to on the website but the link is giving errors
.
Have they had any experience that this was not the best solution or is it
just that the link does not work.

tir. 4. apr. 2023 kl. 09:06 skrev Mich Talebzadeh :

> 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
> Palantir Technologies Limited
>
>
>view my Linkedin profile
> 
>
>
>  https://en.everybodywiki.com/Mich_Talebzadeh
>
>
>
> *Disclaimer:* Use it at your own risk. Any and all responsibility for any
> loss, damage or destruction of data or any other property which may arise
> from relying on this email's technical content is explicitly disclaimed.
> The author will in no case be liable for any monetary damages arising from
> such loss, damage or destruction.
>
>
>
>
> On Tue, 4 Apr 2023 at 07:06,  wrote:
>
>> Hey Dongjoon, Denny and all,
>>
>> I’ve created the current slack.
>> All users have the option to create channels for different topics.
>>
>> I don’t see a reason for creating a new one.
>>
>> If anyone want to be admin on the current slack channel you all are
>> welcome to send me a msg and I’ll grand permission.
>>
>> Have a great week,
>> Shani Alisar
>>
>>
>>
>>
>>
>> On 4 Apr 2023, at 3:51, Dongjoon Hyun  wrote:
>>
>> 
>> Thank you, Denny.
>>
>> May I interpret your comment as a request to support multiple channels in
>> ASF too?
>>
>> > because it would allow us to create multiple channels for different
>> topics
>>
>> Any other reasons?
>>
>> Dongjoon.
>>
>>
>> On Mon, Apr 3, 2023 at 5:31 PM Denny Lee  wrote:
>>
>>> I do think creating a new Slack channel would be helpful because it
>>> would allow us to create multiple channels for different topics -
>>> streaming, graph, ML, etc.
>>>
>>> We would need a volunteer core to maintain it so we can keep the spirit
>>> and letter of ASF / code of conduct.  I’d be glad to volunteer to keep this
>>> active.
>>>
>>>
>>>
>>> On Mon, Apr 3, 2023 at 16:46 Dongjoon Hyun 
>>> wrote:
>>>
 Shall we summarize the discussion so far?

 To sum up, "ASF Slack" vs "3rd-party Slack" was the real background to
 initiate this thread instead of "Slack" vs "Mailing list"?

 If ASF Slack provides what you need, is it better than creating a
 new Slack channel?

 Or, is there another reason for us to create a new Slack channel?

 Dongjoon.


 On Mon, Apr 3, 2023 at 3:27 PM Mich Talebzadeh <
 mich.talebza...@gmail.com> wrote:

> I agree, whatever individual sentiments are.
>
> Mich Talebzadeh,
> Lead Solutions Architect/Engineering Lead
> Palantir Technologies Limited
>
>
>view my Linkedin profile
> 
>
>
>  https://en.everybodywiki.com/Mich_Talebzadeh
>
>
>
> *Disclaimer:* Use it at your own risk. Any and all responsibility for
> any loss, damage or destruction of data or any other property which may
> arise from relying on this email's technical content is explicitly
> disclaimed. The author will in no case be liable for any monetary damages
> arising from such loss, damage or destruction.
>
>
>
>
> On Mon, 3 Apr 2023 at 23:21, Jungtaek Lim <
> kabhwan.opensou...@gmail.com> wrote:
>
>> Just to be clear, if there is no strong volunteer to make the new
>> community channel stay active, I'd probably be OK to not fork the 
>> channel.
>> You can see a strong counter example from #spark channel in ASF. It is 
>> the
>> place where there are only questions and promos but zero answers. I see
>> volunteers here demanding for another channel, so I want to see us go 
>> with
>> the most preferred way for these volunteers.
>>
>> User mailing list does not go in a good shape. I hope we give another
>> try with recent technology to see whether we can gain traction - if we
>> fail, the user mailing list will still be there.
>>
>> On Tue, Apr 4, 2023 at 7:04 AM Jungtaek Lim <
>> kabhwan.opensou...@gmail.com> wrote:
>>
>>> The number of subscribers doesn't give any meaningful value. Pl

Re: Slack for PySpark users

2023-04-04 Thread Mich Talebzadeh 
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
Palantir Technologies Limited


   view my Linkedin profile



 https://en.everybodywiki.com/Mich_Talebzadeh



*Disclaimer:* Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.




On Tue, 4 Apr 2023 at 07:06,  wrote:

> Hey Dongjoon, Denny and all,
>
> I’ve created the current slack.
> All users have the option to create channels for different topics.
>
> I don’t see a reason for creating a new one.
>
> If anyone want to be admin on the current slack channel you all are
> welcome to send me a msg and I’ll grand permission.
>
> Have a great week,
> Shani Alisar
>
>
>
>
>
> On 4 Apr 2023, at 3:51, Dongjoon Hyun  wrote:
>
> 
> Thank you, Denny.
>
> May I interpret your comment as a request to support multiple channels in
> ASF too?
>
> > because it would allow us to create multiple channels for different
> topics
>
> Any other reasons?
>
> Dongjoon.
>
>
> On Mon, Apr 3, 2023 at 5:31 PM Denny Lee  wrote:
>
>> I do think creating a new Slack channel would be helpful because it would
>> allow us to create multiple channels for different topics - streaming,
>> graph, ML, etc.
>>
>> We would need a volunteer core to maintain it so we can keep the spirit
>> and letter of ASF / code of conduct.  I’d be glad to volunteer to keep this
>> active.
>>
>>
>>
>> On Mon, Apr 3, 2023 at 16:46 Dongjoon Hyun 
>> wrote:
>>
>>> Shall we summarize the discussion so far?
>>>
>>> To sum up, "ASF Slack" vs "3rd-party Slack" was the real background to
>>> initiate this thread instead of "Slack" vs "Mailing list"?
>>>
>>> If ASF Slack provides what you need, is it better than creating a
>>> new Slack channel?
>>>
>>> Or, is there another reason for us to create a new Slack channel?
>>>
>>> Dongjoon.
>>>
>>>
>>> On Mon, Apr 3, 2023 at 3:27 PM Mich Talebzadeh <
>>> mich.talebza...@gmail.com> wrote:
>>>
 I agree, whatever individual sentiments are.

 Mich Talebzadeh,
 Lead Solutions Architect/Engineering Lead
 Palantir Technologies Limited


view my Linkedin profile
 


  https://en.everybodywiki.com/Mich_Talebzadeh



 *Disclaimer:* Use it at your own risk. Any and all responsibility for
 any loss, damage or destruction of data or any other property which may
 arise from relying on this email's technical content is explicitly
 disclaimed. The author will in no case be liable for any monetary damages
 arising from such loss, damage or destruction.




 On Mon, 3 Apr 2023 at 23:21, Jungtaek Lim 
 wrote:

> Just to be clear, if there is no strong volunteer to make the new
> community channel stay active, I'd probably be OK to not fork the channel.
> You can see a strong counter example from #spark channel in ASF. It is the
> place where there are only questions and promos but zero answers. I see
> volunteers here demanding for another channel, so I want to see us go with
> the most preferred way for these volunteers.
>
> User mailing list does not go in a good shape. I hope we give another
> try with recent technology to see whether we can gain traction - if we
> fail, the user mailing list will still be there.
>
> On Tue, Apr 4, 2023 at 7:04 AM Jungtaek Lim <
> kabhwan.opensou...@gmail.com> wrote:
>
>> The number of subscribers doesn't give any meaningful value. Please
>> look into the number of mails being sent to the list.
>>
>> https://lists.apache.org/list.html?u...@spark.apache.org
>> The latest month there were more than 200 emails being sent was Feb
>> 2022, more than a year ago. It was more than 1k in 2016, and more than 2k
>> in 2015 and earlier.
>> Let's face the fact. User mailing list is dying, even before we start
>> discussion about alternative communication methods.
>>
>> Users never go with the way if it's just because PMC members (or ASF)
>> have preference. They are going with the way they are convenient.
>>
>> Same applies here - if ASF Slack requires a restricted invitation
>> mechanism then it won't work. Looks like there is a link for an 
>> invitation,
>> but we are also talking about the cost as well.
>> https://cwiki.apache.org/confluence/display/INFRA/Slack+Guest+Invites
>> As long as we are being serious ab