Re: [VOTE] Single-pass Analyzer for Catalyst

+1, Thanks Jie Yang On 2024/10/01 03:26:40 John Zhuge wrote: > +1 (non-binding) > > On Mon, Sep 30, 2024 at 7:42 PM Gengliang Wang > wrote: > > > +1 > > > > On Mon, Sep 30, 2024 at 6:22 PM Jungtaek Lim > > wrote: > > > >> +1 (non-binding), promising proposal! > >> > >> 2024년 10월 1일 (화) 오전 8:0

Re: [VOTE] Single-pass Analyzer for Catalyst

+1, Thanks Jie Yang On 2024/10/01 03:26:40 John Zhuge wrote: > +1 (non-binding) > > On Mon, Sep 30, 2024 at 7:42 PM Gengliang Wang > wrote: > > > +1 > > > > On Mon, Sep 30, 2024 at 6:22 PM Jungtaek Lim > > wrote: > > > >> +1 (non-binding), promising proposal! > >> > >> 2024년 10월 1일 (화) 오전 8:0

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1, Thanks Jie Yang On 2024/10/01 02:53:11 Mridul Muralidharan wrote: > +1. > > Regards, > Mridul > > PS: In the past, I did have fun with graphx ... unfortunate that it has > come to this :-( > > > On Mon, Sep 30, 2024 at 6:23 PM Sean Owen wrote: > > > For reasons in the previous thread, y

Re: [VOTE] Single-pass Analyzer for Catalyst

Folks, thanks for voting! Yes, the target version was set by my mistake, Dongjoon. Sorry for that. Vladimir. On Tue, Oct 1, 2024, 05:28 John Zhuge wrote: > +1 (non-binding) > > On Mon, Sep 30, 2024 at 7:42 PM Gengliang Wang > wrote: > >> +1 >> >> On Mon, Sep 30, 2024 at 6:22 PM Jungtaek Lim <

Re: [VOTE] Single-pass Analyzer for Catalyst

+1 (non-binding) On Mon, Sep 30, 2024 at 7:42 PM Gengliang Wang wrote: > +1 > > On Mon, Sep 30, 2024 at 6:22 PM Jungtaek Lim > wrote: > >> +1 (non-binding), promising proposal! >> >> 2024년 10월 1일 (화) 오전 8:04, Dongjoon Hyun 님이 작성: >> >>> Thank you for the swift clarification, Reynold and Xiao. >

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1. Regards, Mridul PS: In the past, I did have fun with graphx ... unfortunate that it has come to this :-( On Mon, Sep 30, 2024 at 6:23 PM Sean Owen wrote: > For reasons in the previous thread, yes +1 to deprecation > > On Mon, Sep 30, 2024 at 1:02 PM Holden Karau > wrote: > >> I think it

Re: [VOTE] Single-pass Analyzer for Catalyst

+1 Regards, Mridul On Mon, Sep 30, 2024 at 5:39 PM Reynold Xin wrote: > I don't actually "lead" this. But I don't think this needs to target a > specific Spark version given it should not have any user facing > consequences? > > > On Mon, Sep 30, 2024 at 3:36 PM Dongjoon Hyun wrote: > >> Thank

Re: [VOTE] Single-pass Analyzer for Catalyst

+1 On Mon, Sep 30, 2024 at 6:22 PM Jungtaek Lim wrote: > +1 (non-binding), promising proposal! > > 2024년 10월 1일 (화) 오전 8:04, Dongjoon Hyun 님이 작성: > >> Thank you for the swift clarification, Reynold and Xiao. >> >> It seems that the Target Version was set mistakenly initially. >> >> I removed the

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1 (non-binding) 2024년 10월 1일 (화) 오전 8:19, Sean Owen 님이 작성: > For reasons in the previous thread, yes +1 to deprecation > > On Mon, Sep 30, 2024 at 1:02 PM Holden Karau > wrote: > >> I think it has been de-facto deprecated, we haven’t updated it >> meaningfully in several years. I think removing

Re: [VOTE] Single-pass Analyzer for Catalyst

+1 (non-binding), promising proposal! 2024년 10월 1일 (화) 오전 8:04, Dongjoon Hyun 님이 작성: > Thank you for the swift clarification, Reynold and Xiao. > > It seems that the Target Version was set mistakenly initially. > > I removed the `Target Version` from the SPIP JIRA. > > https://issues.apache.org/j

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

For reasons in the previous thread, yes +1 to deprecation On Mon, Sep 30, 2024 at 1:02 PM Holden Karau wrote: > I think it has been de-facto deprecated, we haven’t updated it > meaningfully in several years. I think removing the API would be excessive > but deprecating it would give us the flexi

Re: [VOTE] Single-pass Analyzer for Catalyst

Thank you for the swift clarification, Reynold and Xiao. It seems that the Target Version was set mistakenly initially. I removed the `Target Version` from the SPIP JIRA. https://issues.apache.org/jira/browse/SPARK-49834 I'm switching my cast to +1 for this SPIP vote. Thanks, Dongjoon. On 202

Re: [VOTE] Single-pass Analyzer for Catalyst

+1 in support of the direction of the Single-pass Analyzer for Catalyst. I think we should not have a target version for the new Catalyst SPARK-49834 . It should not be a blocker for Spark 4.0. When implementing the new analyzer, the code changes

Re: [VOTE] Single-pass Analyzer for Catalyst

I don't actually "lead" this. But I don't think this needs to target a specific Spark version given it should not have any user facing consequences? On Mon, Sep 30, 2024 at 3:36 PM Dongjoon Hyun wrote: > Thank you for leading this, Vladimir, Reynold, Herman. > > I'm wondering if this is really

Re: [VOTE] Single-pass Analyzer for Catalyst

Thank you for leading this, Vladimir, Reynold, Herman. I'm wondering if this is really achievable goal for Apache Spark 4.0.0. If it's expected that we are unable to deliver it, shall we postpone this vote until 4.1.0 planning? Anyway, since SPARK-49834 has a target version 4.0.0 explicitly,

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1 On Mon, Sep 30, 2024 at 1:25 PM Herman van Hovell wrote: > > +1 > > On Mon, Sep 30, 2024 at 12:21 PM Dongjoon Hyun wrote: >> >> +1 >> >> Thank you, Holden. >> >> Dongjoon. >> >> On 2024/09/30 18:01:17 Holden Karau wrote: >> > I think it has been de-facto deprecated, we haven’t updated it mean

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1 On Mon, Sep 30, 2024 at 12:21 PM Dongjoon Hyun wrote: > +1 > > Thank you, Holden. > > Dongjoon. > > On 2024/09/30 18:01:17 Holden Karau wrote: > > I think it has been de-facto deprecated, we haven’t updated it > meaningfully > > in several years. I think removing the API would be excessive bu

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1 Mich Talebzadeh, Architect | Data Engineer | Data Science | Financial Crime PhD Imperial College London London, United Kingdom view my Linkedin profile

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1 Thank you, Holden. Dongjoon. On 2024/09/30 18:01:17 Holden Karau wrote: > I think it has been de-facto deprecated, we haven’t updated it meaningfully > in several years. I think removing the API would be excessive but > deprecating it would give us the flexibility to remove it in the not too

[VOTE] Officialy Deprecate GraphX in Spark 4

I think it has been de-facto deprecated, we haven’t updated it meaningfully in several years. I think removing the API would be excessive but deprecating it would give us the flexibility to remove it in the not too distant future. That being said this is not a vote to remove GraphX, I think that w

Re: [VOTE] Single-pass Analyzer for Catalyst

+1 On Mon, Sep 30, 2024 at 8:29 AM Reynold Xin wrote: > +1 > > On Mon, Sep 30, 2024 at 6:47 AM Vladimir Golubev > wrote: > >> Hi all, >> >> I’d like to start a vote for a single-pass Analyzer for the Catalyst >> project. This project will introduce a new analysis framework to the >> Catalyst, w

Re: [DISCUSS] Deprecate GraphX OR Find new maintainers interested in GraphX OR leave it as is?

I support deprecating GraphX because: - GraphFrames supersedes it, really - No maintainers and no reason to believe there will be - we can take the last 5+ years as thorough evidence - Low (but not trivial) docs hits compared to other modules: https://analytics.apache.org/index.php

Re: [VOTE] Single-pass Analyzer for Catalyst

+1 On Mon, Sep 30, 2024 at 6:47 AM Vladimir Golubev wrote: > Hi all, > > I’d like to start a vote for a single-pass Analyzer for the Catalyst > project. This project will introduce a new analysis framework to the > Catalyst, which will eventually replace the fixed-point one. > > Please refer to

[VOTE] Single-pass Analyzer for Catalyst

Hi all, I’d like to start a vote for a single-pass Analyzer for the Catalyst project. This project will introduce a new analysis framework to the Catalyst, which will eventually replace the fixed-point one. Please refer to the SPIP jira: https://issues.apache.org/jira/browse/SPARK-49834 [ ] +1:

Re: [DISCUSS] Deprecate GraphX OR Find new maintainers interested in GraphX OR leave it as is?

Hi, These are my Views: 1. Deprecation Consideration: I lean towards the idea of officially deprecating GraphX, given the lack of active development and community engagement over the past few years as you alluded. This would set clear expectations for users about its future and encourage them to