Responses in line Twitter: https://twitter.com/holdenkarau Fight Health Insurance: https://www.fighthealthinsurance.com/ <https://www.fighthealthinsurance.com/?q=hk_email> Books (Learning Spark, High Performance Spark, etc.): https://amzn.to/2MaRAG9 <https://amzn.to/2MaRAG9> YouTube Live Streams: https://www.youtube.com/user/holdenkarau Pronouns: she/her
On Wed, Nov 13, 2024 at 8:47 AM Denny Lee <denny.g....@gmail.com> wrote: > > If by "at length" you mean ... among very few people, in a very few > emails, throughout less than a week. Yes, you're totally right. > > The implication that this was a rash decision decided by a few people in a > short amount of time is incorrect. > +1 > > This discussion all started on the thread "[VOTE] Officialy Deprecate > GraphX in Spark 4" that started on September 30th. The result of the vote > being twelve +1 and two -1 per the thread dated October 7th. > on top of that it’s not like this is the first time folks have thought about deprecating graph X back in *2017* the lack of maintenance was raised leading to the question “Is GraphX Really Deprecated?” — https://lists.apache.org/thread/o61cgx0q4h4m9rcjxczy010gwjz0zn7z Since then there have been discussions on this and other threads to the > Spark dev list with folks volunteering to help bring it back (cool!). > This is really exciting :) And it’s never happened in the previous iterations. I think something about something actually maybe going away draws people to action > And we're continuing the conversation here in mid-November. > And that’s good-ish. I love that folks are thinking about how to keep this component alive. I don’t love that we keep circling back to a decision we’ve already made with the implication that it was made improperly. I think undeprecation can be revisited *if and only if* we’ve got reasonable development work happening in the component. > > > > >
