Re: Re: [VOTE] SPARK-44444: Use ANSI SQL mode by default

2024-04-15 Thread Rui Wang
+1, non-binding. Thanks Dongjoon to drive this! -Rui On Mon, Apr 15, 2024 at 10:10 AM Xinrong Meng wrote: > +1 > > Thank you @Dongjoon Hyun ! > > On Mon, Apr 15, 2024 at 6:33 AM beliefer wrote: > >> +1 >> >> >> 在 2024-04-15 15:54:07,"Peter Toth" 写道: >> >> +1 >> >> Wenchen Fan ezt írta

Re: Welcome to Our New Apache Spark Committer and PMCs

2023-10-03 Thread Rui Wang
Congratulations! Well deserved! -Rui On Mon, Oct 2, 2023 at 10:32 PM Gengliang Wang wrote: > Congratulations to all! Well deserved! > > On Mon, Oct 2, 2023 at 10:16 PM Xiao Li wrote: > >> Hi all, >> >> The Spark PMC is delighted to announce that we have voted to add one new >> committer and

Re: [ANNOUNCE] Apache Spark 3.4.0 released

2023-04-19 Thread Rui Wang
Thank you, Xinrong! -Rui On Mon, Apr 17, 2023 at 10:05 AM Xinrong Meng wrote: > Thank you, Dongjoon! > > On Sat, Apr 15, 2023 at 9:04 AM Dongjoon Hyun > wrote: > >> Nice catch, Xiao! >> >> All `latest` tags are updated to v3.4.0 now. >> >> https://hub.docker.com/r/apache/spark/tags >>

Re: The Spark email setting should be update

2023-04-19 Thread Rui Wang
I am replying now and the default address is dev@spark.apache.org. -Rui On Mon, Apr 17, 2023 at 4:27 AM Jia Fan wrote: > Hi, everyone. > > I find that every time I reply to dev's mailing list, the default address > of the reply is the sender of the mail, not dev@spark.apache.org. It > caused

Re: Time for Spark 3.4.0 release?

2023-01-03 Thread Rui Wang
+1 to cut the branch starting from a workday! Great to see this is happening! Thanks Xinrong! -Rui On Tue, Jan 3, 2023 at 9:21 PM 416161...@qq.com wrote: > +1, thank you Xinrong for driving this release! > > -- > Ruifeng Zheng > ruife...@foxmail.com > >

Re: Welcome Yikun Jiang as a Spark committer

2022-10-18 Thread Rui Wang
Well deserved! Congrats! -Rui On Mon, Oct 10, 2022 at 9:07 AM Xinrong Meng wrote: > Congratulations, Yikun! Well deserved. > > On Sun, Oct 9, 2022 at 9:36 PM John Zhuge wrote: > >> Congratulations, Yikun! >> >> On Sun, Oct 9, 2022 at 8:52 PM Senthil Kumar wrote: >> >>> Congratulations Yikun

Re: [DISCUSS] [Spark SQL, PySpark] Combining StructTypes into a new StructType

2022-08-09 Thread Rui Wang
Thanks for the idea! I am thinking that the usage of "combined = StructType( a.fields + b.fields)" is still good because 1) it is not horrible to merge a and b in this way. 2) itself clarifies the intention which is merge two struct's fields to construct a new struct 3) you also have room to

Re: Welcome Xinrong Meng as a Spark committer

2022-08-09 Thread Rui Wang
Congrats Xinrong! -Rui On Tue, Aug 9, 2022 at 8:57 PM Xingbo Jiang wrote: > Congratulations! > > Yuanjian Li 于2022年8月9日 周二20:31写道: > >> Congratulations, Xinrong! >> >> XiDuo You 于2022年8月9日 周二19:18写道: >> >>> Congratulations! >>> >>> Haejoon Lee 于2022年8月10日周三 09:30写道: >>> > >>> > Congrats,

Re: Update Spark 3.4 Release Window?

2022-07-21 Thread Rui Wang
+1 for code freeze in Jan 2023 then QA period and then RC in Feb 2023. -Rui On Thu, Jul 21, 2022 at 11:46 AM Chao Sun wrote: > +1 for Jan 2023 (Code freeze) and Feb 2023 (RC). > > Chao > > On Thu, Jul 21, 2022 at 11:43 AM L. C. Hsieh wrote: > > > > I'm also +1 for Feb. 2023 (RC) and Jan.

Re: [DISCUSS][Catalog API] Deprecate 4 Catalog API that takes two parameters which are (dbName, tableName/functionName)

2022-07-14 Thread Rui Wang
et us know if you don't agree. -Rui On Fri, Jul 8, 2022 at 11:18 AM Rui Wang wrote: > Yes. The current goal is a pure educational deprecation. > > So given the proposal: > 1. existing users or users who do not care about catalog names in table > identifiers can still use

Re: [DISCUSS][Catalog API] Deprecate 4 Catalog API that takes two parameters which are (dbName, tableName/functionName)

2022-07-08 Thread Rui Wang
ion and allow >> users to use both APIs freely without any concern of uncertain >> insupportability? I simply want to avoid the situation where the pure >> educational deprecation itself becomes `Unneeded Deprecation` in the >> community. >> >> Dongjoon. >&g

Re: [DISCUSS][Catalog API] Deprecate 4 Catalog API that takes two parameters which are (dbName, tableName/functionName)

2022-07-07 Thread Rui Wang
I want to highlight in case I missed this in the original email: The 4 API will not be deleted. They will just be marked as deprecated annotations and we encourage users to use their alternatives. -Rui On Thu, Jul 7, 2022 at 2:23 PM Rui Wang wrote: > Hi Community, > > Proposal:

[DISCUSS][Catalog API] Deprecate 4 Catalog API that takes two parameters which are (dbName, tableName/functionName)

2022-07-07 Thread Rui Wang
4. There was existing practice that we deprecated CreateExternalTable API when adding CreateTable API: https://github.com/apache/spark/blob/7dcb4bafd02dd43213d3cc4a936c170bda56ddc5/sql/core/src/main/scala/org/apache/spark/sql/catalog/Catalog.scala#L220 What do you think? Thanks, Rui Wang