Re: [VOTE] Officialy Deprecate GraphX in Spark 4

The VOTE is now closed and I believe it passes*, albeit with notable dissent. The votes are: +1: Mich Talebzadeh Dongjoon Hyun LC Hsieh Sean Owen Jungtaek Lim Mridul Muralidharan Yang Jie beliefer Wenchen Fan Denny Lee Hyukjin Kwon Herman van Hovell 0s: -1: Mark Hamstra Ángel While not on th

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1 Twitter: https://twitter.com/holdenkarau Fight Health Insurance: https://www.fighthealthinsurance.com/ Books (Learning Spark, High Performance Spark, etc.): https://amzn.to/2MaRAG9 YouTube Live Streams: https://www.yo

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

-1(*) reasoning posted in the DISCUSS thread On Mon, Sep 30, 2024 at 12:40 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 flexibility to

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

The graphframes library depends on GraphX and has changed recently (3 months ago). https://github.com/graphframes/graphframes/blob/master/src/main/scala/org/graphframes/GraphFrame.scala El vie, 4 oct 2024, 11:35, Nimrod Ofek escribió: > Hi, > > Did anyone do any search about the GraphX API i

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

FWIW, this is a Google Search trend in last 5 years: [image: Screenshot 2024-10-04 at 6.54.42 PM.png] I think it's fine to deprecate it On Fri, 4 Oct 2024 at 18:40, Nimrod Ofek wrote: > Hi, > > Did anyone do any search about the GraphX API in Gitlab/Github and > different search engines to see

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

Hi, Did anyone do any search about the GraphX API in Gitlab/Github and different search engines to see if they are searched and actually used - or we are considering it not used because the API wasn't changed? Thanks! Nimrod On Mon, Sep 30, 2024 at 9:02 PM Holden Karau wrote: > I think it has

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1 On Fri, 4 Oct 2024 at 07:14, Ángel wrote: > -1 Don’t deprecate GraphX because may be useful for some people and ... > would there be any replacement for that API? Anyway, I don't think > deprecating an API only because it hasn't been updated in ages is a good > practice (but I could be perfec

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

-1 Don’t deprecate GraphX because may be useful for some people and ... would there be any replacement for that API? Anyway, I don't think deprecating an API only because it hasn't been updated in ages is a good practice (but I could be perfectly wrong). El jue, 3 oct 2024, 16:31, Wenchen Fan esc

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1 (non-binding) On Thu, Oct 3, 2024 at 7:40 AM Wenchen Fan wrote: > +1 > > On Tue, Oct 1, 2024 at 4:20 PM beliefer wrote: > >> +1. >> >> I didn't hear users need it. >> >> >> At 2024-10-01 02:01:17, "Holden Karau" wrote: >> >> I think it has been de-facto deprecated, we haven’t updated it >>

Re: [VOTE] Officialy Deprecate GraphX in Spark 4

+1 On Tue, Oct 1, 2024 at 4:20 PM beliefer wrote: > +1. > > I didn't hear users need it. > > > At 2024-10-01 02: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 depr

Re:[VOTE] Officialy Deprecate GraphX in Spark 4

+1. I didn't hear users need it. At 2024-10-01 02: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

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] 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] 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] 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] 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