Re: [外部邮件] Re: [VOTE] Move Spark Connect server to builtin package (Client API layer stays external)

+1 (non-binding), Kent Martin Grund 于2024年7月3日周三 14:11写道： > > +1 (non-binding) > > On Wed, Jul 3, 2024 at 07:25 Holden Karau wrote: >> >> +1 >> >> Twitter: https://twitter.com/holdenkarau >> Books (Learning Spark, High Performance Spark, etc.): https://amzn.to/2MaRAG9 >> YouTube Live Streams: h

Re: [VOTE] Move Spark Connect server to builtin package (Client API layer stays external)

+1 (non-binding) Thanks, Cheng Pan > On Jul 3, 2024, at 08:59, Hyukjin Kwon wrote: > > Hi all, > > I’d like to start a vote for moving Spark Connect server to builtin package > (Client API layer stays external). > > Please also refer to: > >- Discussion thread: > https://lists.apache.

Re: [外部邮件] Re: [VOTE] Move Spark Connect server to builtin package (Client API layer stays external)

+1 (non-binding) On Wed, Jul 3, 2024 at 07:25 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 > > >

Re: [外部邮件] Re: [VOTE] Move Spark Connect server to builtin package (Client API layer stays external)

+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 On Tue, Jul 2, 2024 at 10:18 PM yangjie01 wrote: > +1 (non-binding) > > > > *发件人**

Re: [外部邮件] Re: [VOTE] Move Spark Connect server to builtin package (Client API layer stays external)

+1 (non-binding) 发件人: Denny Lee 日期: 2024年7月3日 星期三 09:12 收件人: Hyukjin Kwon 抄送: dev 主题: [外部邮件] Re: [VOTE] Move Spark Connect server to builtin package (Client API layer stays external) +1 (non-binding) On Wed, Jul 3, 2024 at 9:11 AM Hyukjin Kwon mailto:gurwls...@apache.org>> wrote: Starting w

Deploying Spark on Kubernetes Operator

Hello Spark team, I hope this email finds you well. I am writing on behalf of my team, which is looking to deploy a Spark Kubernetes Operator in our cluster. We have come across this latest initiative on GitHub to develop a Java based operator

Re: [VOTE] Move Spark Connect server to builtin package (Client API layer stays external)

+1 (non-binding) On Wed, Jul 3, 2024 at 9:11 AM Hyukjin Kwon wrote: > Starting with my own +1. > > On Wed, 3 Jul 2024 at 09:59, Hyukjin Kwon wrote: > >> Hi all, >> >> I’d like to start a vote for moving Spark Connect server to builtin >> package (Client API layer stays external). >> >> Please a

Re: [VOTE] Move Spark Connect server to builtin package (Client API layer stays external)

Starting with my own +1. On Wed, 3 Jul 2024 at 09:59, Hyukjin Kwon wrote: > Hi all, > > I’d like to start a vote for moving Spark Connect server to builtin > package (Client API layer stays external). > > Please also refer to: > >- Discussion thread: > https://lists.apache.org/thread/odlx9b5

[VOTE] Move Spark Connect server to builtin package (Client API layer stays external)

Hi all, I’d like to start a vote for moving Spark Connect server to builtin package (Client API layer stays external). Please also refer to: - Discussion thread: https://lists.apache.org/thread/odlx9b552dp8yllhrdlp24pf9m9s4tmx - JIRA ticket: https://issues.apache.org/jira/browse/SPARK-4876

Re: [DISCUSS] Move Spark Connect server to builtin package (Client API layer stays external)

Alrighty, let me start the vote to make sure everybody is happy :-). On Wed, 3 Jul 2024 at 09:55, Hyukjin Kwon wrote: > It will be fine for non-connect users. When we are actually moving client > one, I think we should go with an SPIP cuz that might affect end users > > On Tue, 2 Jul 2024 at

Re: [DISCUSS] Move Spark Connect server to builtin package (Client API layer stays external)

It will be fine for non-connect users. When we are actually moving client one, I think we should go with an SPIP cuz that might affect end users On Tue, 2 Jul 2024 at 23:05, Holden Karau wrote: > I guess my one concern here would be are we going to expand the > dependencies that are visible

Re: [DISCUSS] Move Spark Connect server to builtin package (Client API layer stays external)

I guess my one concern here would be are we going to expand the dependencies that are visible on the class path for non-connect users? One of the pain points that folks experienced with upgrading can be from those changing. Otherwise this seems pretty reasonable. Twitter: https://twitter.com/hol

Re: [DISCUSS] Move Spark Connect server to builtin package (Client API layer stays external)

This is a great idea and would be a great quality of life improvement. +1 (non-binding) On Tue, Jul 2, 2024 at 4:56 AM Hyukjin Kwon wrote: > > while leaving the connect jvm client in a separate folder looks weird > > I plan to actually put it at the top level together but I feel like this > has

Re: [DISCUSS] Move Spark Connect server to builtin package (Client API layer stays external)

> while leaving the connect jvm client in a separate folder looks weird I plan to actually put it at the top level together but I feel like this has to be done with SPIP so I am moving internal server side first orthogonally On Tue, 2 Jul 2024 at 17:54, Cheng Pan wrote: > Thanks for raising thi

Re: [DISCUSS] Move Spark Connect server to builtin package (Client API layer stays external)

Thanks for raising this discussion, I think putting the connect folder on the top level is a good idea to promote Spark Connect, while leaving the connect jvm client in a separate folder looks weird. I suppose there is no contract to leave all optional modules under `connector`? e.g. `resource-

Re: [外部邮件] [DISCUSS] Move Spark Connect server to builtin package (Client API layer stays external)

+1 On Tue, Jul 2, 2024 at 7:19 AM yangjie01 wrote: > I have manually attempted to only modify the `assembly/pom.xml` and > examined the results of executing `dev/make-distribution.sh --tgz`. The > `spark-connect_2.13-4.0.0-SNAPSHOT.jar` is indeed included in the jars > directory. However, if rea