Re: Time for Spark 3.4.0 release?

Yeah, these more look like something we should discuss around RC timing. See "Spark 3.4 release window" in https://spark.apache.org/versioning-policy.html On Wed, 18 Jan 2023 at 16:28, Enrico Minack wrote: > You are saying the RCs are cut from that branch at a later point? What is > the

Re: Time for Spark 3.4.0 release?

You are saying the RCs are cut from that branch at a later point? What is the estimate deadline for that? Enrico Am 18.01.23 um 07:59 schrieb Hyukjin Kwon: These look like we can fix it after the branch-cut so should be fine. On Wed, 18 Jan 2023 at 15:57, Enrico Minack wrote: Hi

Re: Time for Spark 3.4.0 release?

These look like we can fix it after the branch-cut so should be fine. On Wed, 18 Jan 2023 at 15:57, Enrico Minack wrote: > Hi Xinrong, > > what about regression issue > https://issues.apache.org/jira/browse/SPARK-40819 > and correctness issue https://issues.apache.org/jira/browse/SPARK-40885? >

Re: Time for Spark 3.4.0 release?

Hi Xinrong, what about regression issue https://issues.apache.org/jira/browse/SPARK-40819 and correctness issue https://issues.apache.org/jira/browse/SPARK-40885? The latter gets fixed by either https://issues.apache.org/jira/browse/SPARK-41959 or

Re: Time for Spark 3.4.0 release?

+1 on delaying. I see there’s a JIRA ticket about DStream depreciation, we are working on this - thanks for taking this into account! 2023년 1월 18일 (수) 오후 12:43, Hyukjin Kwon 님이 작성: > +1. Thanks for driving this, Xinrong. > > On Wed, 18 Jan 2023 at 12:31, Xinrong Meng > wrote: > >> Hi All, >> >>

Re: Time for Spark 3.4.0 release?

+1. Thanks for driving this, Xinrong. On Wed, 18 Jan 2023 at 12:31, Xinrong Meng wrote: > Hi All, > > Considering there are still important issues unresolved (some are as shown > below), I would suggest to be conservative, we delay the branch-3.4's cut > for one week. > >

Re: Time for Spark 3.4.0 release?

Hi All, Considering there are still important issues unresolved (some are as shown below), I would suggest to be conservative, we delay the branch-3.4's cut for one week. https://issues.apache.org/jira/browse/SPARK-39375 https://issues.apache.org/jira/browse/SPARK-41589

Re: [Suggest] Add geo function to core

Mosaic by Databricks Labs tir. 17. jan. 2023 kl. 15:53 skrev Grigory Pomadchin : > Hey Mo, > > That is awesome, great to hear! > > Best, > > Grigory > > On Tue, Jan 17, 2023 at 9:03 AM Mo Sarwat wrote: > >> Grigory, >> >> Thanks a lot for chiming - I

Re: [Suggest] Add geo function to core

Hey Mo, That is awesome, great to hear! Best, Grigory On Tue, Jan 17, 2023 at 9:03 AM Mo Sarwat wrote: > Grigory, > > Thanks a lot for chiming - I really like the PostGIS to PostgreSQL > analogy. That is exactly what Sedona (an Apache project) is to Spark. Spark > core should remain light /

Re: [Suggest] Add geo function to core

Grigory, Thanks a lot for chiming - I really like the PostGIS to PostgreSQL analogy. That is exactly what Sedona (an Apache project) is to Spark. Spark core should remain light / generic enough (similar to PostgreSQL) and all spatial functionalities should be pluggable extensions (Sedona).