Re: [DISCUSS] Move Variant to Parquet?

+1 In addition to everything said above, it is also a great opportunity for wider testing and possibly tweaking the spec before it takes off post standardization. On Tue, Aug 20, 2024 at 4:36 PM Russell Spitzer wrote: > I think this would be a great move to encourage all sorts of engines and >

Re: [外部邮件] Re: [DISCUSS] Deprecating SparkR

+1 Let's start a vote? On Fri, Aug 16, 2024 at 2:05 AM yangjie01 wrote: > +1 > 原始邮件 > 发件人：Jungtaek Lim > 时间：2024-08-16 09:06:52 > 主题：[外部邮件] Re： [DISCUSS] Deprecating SparkR > 收件人：Wenchen Fan; > 抄送人：L. C. Hsieh;Dongjoon > Hyun;Holden > Karau;Xiao Li;Hyukjin Kwon< > gurwls...@a

Re: [外部邮件] Re: [DISCUSS] Deprecating SparkR

Thanks all! Yes - I will start a vote thread now Shivaram On Wed, Aug 21, 2024 at 10:24 AM Herman van Hovell wrote: > +1 > > Let's start a vote? > > On Fri, Aug 16, 2024 at 2:05 AM yangjie01 > wrote: > >> +1 >> 原始邮件 >> 发件人：Jungtaek Lim >> 时间：2024-08-16 09:06:52 >> 主题：[外部邮件]

Re: [DISCUSS] Deprecating SparkR

Thanks Holden -- this is a good point. I will reach out to sparklyr developers and make sure they are subscribed to the dev mailing list. Thanks Shivaram On Mon, Aug 12, 2024 at 7:52 PM Holden Karau wrote: > +1 > > Are the sparklyr folks on this list? > > Twitter: https://twitter.com/holdenkara

[VOTE] Deprecate SparkR

Hi all Based on the previous discussion thread [1], I hereby call a vote to deprecate the SparkR module in Apache Spark with the upcoming Spark 4 release and remove it in the next major release Spark 5. [ ] +1: Accept the proposal [ ] +0 [ ] -1: I don’t think this is a good idea because .. This

Re: [VOTE] Deprecate SparkR

+1 On Wed, Aug 21, 2024 at 6:42 PM Shivaram Venkataraman < shivaram.venkatara...@gmail.com> wrote: > Hi all > > Based on the previous discussion thread [1], I hereby call a vote to > deprecate the SparkR module in Apache Spark with the upcoming Spark 4 > release and remove it in the next major re

Re: [VOTE] Deprecate SparkR

+1 Regards, Mridul On Wed, Aug 21, 2024 at 11:46 AM Reynold Xin wrote: > +1 > > On Wed, Aug 21, 2024 at 6:42 PM Shivaram Venkataraman < > shivaram.venkatara...@gmail.com> wrote: > >> Hi all >> >> Based on the previous discussion thread [1], I hereby call a vote to >> deprecate the SparkR modu

Re: [VOTE] Deprecate SparkR

+1 On Wed, Aug 21, 2024, 11:40 AM Shivaram Venkataraman < shivaram.venkatara...@gmail.com> wrote: > Hi all > > Based on the previous discussion thread [1], I hereby call a vote to > deprecate the SparkR module in Apache Spark with the upcoming Spark 4 > release and remove it in the next major rel

Re: [VOTE] Deprecate SparkR

+1 (non-binding) On Wed, Aug 21, 2024 at 9:50 AM Sean Owen wrote: > +1 > > On Wed, Aug 21, 2024, 11:40 AM Shivaram Venkataraman < > shivaram.venkatara...@gmail.com> wrote: > >> Hi all >> >> Based on the previous discussion thread [1], I hereby call a vote to >> deprecate the SparkR module in Apa

Re: [VOTE] Deprecate SparkR

+1 On Wed, Aug 21, 2024, 10:24 AM Mridul Muralidharan wrote: > +1 > > > Regards, > Mridul > > > On Wed, Aug 21, 2024 at 11:46 AM Reynold Xin > wrote: > >> +1 >> >> On Wed, Aug 21, 2024 at 6:42 PM Shivaram Venkataraman < >> shivaram.venkatara...@gmail.com> wrote: >> >>> Hi all >>> >>> Based on t

Re: [DISCUSS] Move Variant to Parquet?

Agreed that Parquet would be a good place to host the new type. Different table formats, like Iceberg and Delta can benefit from it as they have based on parquet already. Yufei On Wed, Aug 21, 2024 at 12:15 AM Alkis Evlogimenos wrote: > +1 > > In addition to everything said above, it is also a

Re: [VOTE] Deprecate SparkR

+1 On Wed, Aug 21, 2024 at 20:26 Xiangrui Meng wrote: > +1 > > On Wed, Aug 21, 2024, 10:24 AM Mridul Muralidharan > wrote: > >> +1 >> >> >> Regards, >> Mridul >> >> >> On Wed, Aug 21, 2024 at 11:46 AM Reynold Xin >> wrote: >> >>> +1 >>> >>> On Wed, Aug 21, 2024 at 6:42 PM Shivaram Venkataraman

Re: [VOTE] Deprecate SparkR

+1 On Wed, Aug 21, 2024 at 2:55 PM Martin Grund wrote: > +1 > > On Wed, Aug 21, 2024 at 20:26 Xiangrui Meng wrote: > >> +1 >> >> On Wed, Aug 21, 2024, 10:24 AM Mridul Muralidharan >> wrote: >> >>> +1 >>> >>> >>> Regards, >>> Mridul >>> >>> >>> On Wed, Aug 21, 2024 at 11:46 AM Reynold Xin >>>

Re: [VOTE] Deprecate SparkR

+1 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 Pronouns: she/her On Wed, Aug 21, 2024 at 8:59 PM Herman van Hovell wrote: > +1 >

Re: [VOTE] Deprecate SparkR

+1 Dongjoon On 2024/08/21 19:00:46 Holden Karau wrote: > +1 > > 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 > Pronouns: she/h

Re: Please review (ValidateExternalType should return child in error)

Thank you, Mich. What is the correct procedure to request a review? On Tue, 20 Aug 2024 at 22:57, Mich Talebzadeh wrote: > Hi Mark, > > Added a comment to Jira to provide more clarity to Description > > When encountering mixed schema rows, the current error message "{actual} > is not a valid ex

Re: [VOTE] Deprecate SparkR

+1 (non-binding) Thanks for initiating the discussion and vote. On Thu, Aug 22, 2024 at 5:36 AM Dongjoon Hyun wrote: > +1 > > Dongjoon > > On 2024/08/21 19:00:46 Holden Karau wrote: > > +1 > > > > Twitter: https://twitter.com/holdenkarau > > Books (Learning Spark, High Performance Spark, etc.):

Re: Please review (ValidateExternalType should return child in error)

Hi Mark, You have already done that and have made the request for review. +1 for me Mich Talebzadeh, Architect | Data Engineer | Data Science | Financial Crime PhD Imperial College London

Re: [DISCUSS] Move Variant to Parquet?

+1 for moving variant type to Parquet, as it promotes standardization and interoperability across numerous projects. Huaxin On Wed, Aug 21, 2024 at 1:28 PM Yufei Gu wrote: > Agreed that Parquet would be a good place to host the new type. Different > table formats, like Iceberg and Delta can ben

Re: Spark Reads from MapR and Write to MinIO fails for few batches

Hello Team, Could you please check on this request ? On Mon, Aug 19, 2024 at 7:00 PM Prem Sahoo wrote: > Hello Spark and User, > could you please shed some light ? > > On Thu, Aug 15, 2024 at 7:15 PM Prem Sahoo wrote: > >> Hello Spark and User, >> we have a Spark project which is a long runnin

Re: [DISCUSS] Move Variant to Parquet?

+1, there is a common problem of moving something out, "synchronization of release cadence" but I believe we can make the migration smooth. On Thu, Aug 22, 2024 at 6:54 AM Yufei Gu wrote: > Agreed that Parquet would be a good place to host the new type. Different > table formats, like Iceberg an

Re: [VOTE] Deprecate SparkR

+1 On Thu, 22 Aug 2024 at 05:37, Dongjoon Hyun wrote: > +1 > > Dongjoon > > On 2024/08/21 19:00:46 Holden Karau wrote: > > +1 > > > > Twitter: https://twitter.com/holdenkarau > > Books (Learning Spark, High Performance Spark, etc.): > > https://amzn.to/2MaRAG9 > > YouT

Re: [VOTE] Deprecate SparkR

+1 Hyukjin Kwon 于2024年8月21日周三 16:46写道： > +1 > > On Thu, 22 Aug 2024 at 05:37, Dongjoon Hyun wrote: > >> +1 >> >> Dongjoon >> >> On 2024/08/21 19:00:46 Holden Karau wrote: >> > +1 >> > >> > Twitter: https://twitter.com/holdenkarau >> > Books (Learning Spark, High Performance Spark, etc.): >> > h

Re: [DISCUSS] Move Variant to Parquet?

Parquet is the right project for standardizing the new data type Variant huaxin gao 于2024年8月21日周三 15:26写道： > +1 for moving variant type to Parquet, as it promotes standardization and > interoperability across numerous projects. > > Huaxin > > On Wed, Aug 21, 2024 at 1:28 PM Yufei Gu wrote: > >>

Re: [DISCUSS] Move Variant to Parquet?

+1 too On Wed, Aug 21, 2024 at 4:43 PM huaxin gao wrote: > +1 for moving variant type to Parquet, as it promotes standardization and > interoperability across numerous projects. > > Huaxin > > On Wed, Aug 21, 2024 at 1:28 PM Yufei Gu wrote: > >> Agreed that Parquet would be a good place to host