Re: [VOTE] Release Spark 3.4.1 (RC1)

+1 在 2023/6/21 13:20，“L. C. Hsieh”mailto:vii...@gmail.com>> 写入: +1 On Tue, Jun 20, 2023 at 8:48 PM Dongjoon Hyun mailto:dongj...@apache.org>> wrote: > > +1 > > Dongjoon > > On 2023/06/20 02:51:32 Jia Fan wrote: > > +1 > > > > Dongjoon Hyun mailto:dongj...@apache.org>> > > 于2023年6月20日周二

Re: [VOTE] Release Spark 3.4.1 (RC1)

+1 On Tue, Jun 20, 2023 at 8:48 PM Dongjoon Hyun wrote: > > +1 > > Dongjoon > > On 2023/06/20 02:51:32 Jia Fan wrote: > > +1 > > > > Dongjoon Hyun 于2023年6月20日周二 10:41写道： > > > > > Please vote on releasing the following candidate as Apache Spark version > > > 3.4.1. > > > > > > The vote is open

Re: [VOTE] Release Spark 3.4.1 (RC1)

+1 Dongjoon On 2023/06/20 02:51:32 Jia Fan wrote: > +1 > > Dongjoon Hyun 于2023年6月20日周二 10:41写道： > > > Please vote on releasing the following candidate as Apache Spark version > > 3.4.1. > > > > The vote is open until June 23rd 1AM (PST) and passes if a majority +1 PMC > > votes are cast, with

Re: Apache Spark 4.0.0 Dev Item Planning (SPARK-44111)

Thank you, Yuming. Please update SPARK-44111 by adding links to those JIRA for visibility. Otherwise, we may miss them during the up-coming discussion. Dongjoon. On Tue, Jun 20, 2023 at 6:40 PM Yuming Wang wrote: > Thank you Dongjoon. I'd like to add these items. > > *Support for more SQL

Re: Apache Spark 4.0.0 Dev Item Planning (SPARK-44111)

Thank you Dongjoon. I'd like to add these items. *Support for more SQL syntax* SPARK-31561 Add QUALIFY clause SPARK-24497 Support recursive SQL SPARK-32064

Re: [VOTE][RESULT] Release Plan for Apache Spark 4.0.0 (June 2024)

Ya, it sounds like that. Could you link those items to the following JIRA? https://issues.apache.org/jira/browse/SPARK-44111 Prepare Apache Spark 4.0.0 Dongjoon. On Tue, Jun 20, 2023 at 12:45 PM Holden Karau wrote: > That seems like a really good reason for a major version change given the

Apache Spark 4.0.0 Dev Item Planning (SPARK-44111)

Hi, All. As a continuation of our previous discussion, the official Apache Spark 4.0 Plan JIRA is created today in order to collect the community dev items. Feel free to add your work items, ideas, suggestions, aspirations and interests. We will moderate together.

Re: [VOTE][RESULT] Release Plan for Apache Spark 4.0.0 (June 2024)

That seems like a really good reason for a major version change given the % of PySpark users and the fact we are (effectively) tied to pandas APIs. On Tue, Jun 20, 2023 at 12:24 PM Bjørn Jørgensen wrote: > One big thing for 4.0 will be that pandas API on spark will support pandas > version 2.0

Re: [VOTE][RESULT] Release Plan for Apache Spark 4.0.0 (June 2024)

One big thing for 4.0 will be that pandas API on spark will support pandas version 2.0 With the major release of pandas 2.0.0 on April 3, 2023, numerous breaking changes have been introduced. So, we have made the decision to postpone addressing these breaking changes until the next major release

Re: [DISCUSS] SPIP: Python Data Source API

In an ideal world, every data source you want to connect to already has a Spark data source implementation (either v1 or v2), then this Python API is useless. But I feel it's common that people want to do quick data exploration, and the target data system is not popular enough to have an existing

unsubscribe

-- Thanks, Bhargava Sukkala. Cell no:216-278-1066 MS in Business Analytics, Arizona State University.

Re: [VOTE] Apache Spark PMC asks Databricks to differentiate its Spark version string

+0 A PMC member raised a justified concern regarding the Apache Spark trademark usage. Based on the linked discussion on @legal, that opinion seems to be weakly supported by the ASF Legal Affairs Assistant V.P. As such, it shouldn't just be rejected, especially not because of our preference

Re: [DISCUSS] SPIP: Python Data Source API

Similarly to Jacek, I feel it fails to document an actual community need for such a feature. Currently, any data source implementation has the potential to benefit Spark users across all supported and third-party clients. For generally available sources, this is advantageous for the whole