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

This should be taken offline - this is cross-posting to thousands of people. On Mon, Nov 18, 2024 at 12:37 PM Russell Jurney wrote: > I think we need a unit test that shows inconsistent results with the old > code and not with the new. I have one working, if I can just get the tests > to run wit

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

I think we need a unit test that shows inconsistent results with the old code and not with the new. I have one working, if I can just get the tests to run without formatting issues. Still getting the environment setup. On Mon, Nov 18, 2024 at 2:44 AM awadhesh singh wrote: > Hi Russell > > I have

Re: Vulnerabilities found on pyspark

Actually, that page is about something different: that page lists security advisories in previous versions of Spark itself, while KMBL are sharing the fact that there are advisories for dependencies of pyspark. On Mon, Nov 18, 2024 at 5:16 PM vaquar khan wrote: > > Hi Kamal , > Please check apach

Re: Vulnerabilities found on pyspark

Hi Kamal , Please check apache spark security advisory all crtical issue mentioned here. https://spark.apache.org/security.html Regards, Vaquar khan On Mon, Nov 18, 2024, 9:37 AM Arnout Engelen wrote: > Hello Kamal et al, > > Thank you for your message! In the future, please don't use > secur

Re: Vulnerabilities found on pyspark

Hello Kamal et al, Thank you for your message! In the future, please don't use secur...@spark.apache.org for reports such as this one: if there is an advisory for a dependency, more often than not, the dependency is not used in a way that is impacted by the advisory. As such we don't consider repo

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

Hi Russell I have made the change suggested in jira and was able to run the tests after building. Opened up a PR . Can you review it? Regards Awadhesh On Mon, Nov 18, 2024 at 1:57 PM Russell Jurney wrote: > Thanks, I'm working on SPARK-42856 but the

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

Thanks, I'm working on SPARK-42856 but the tests fail due to formatting issues - confusing as I ran scalafmt. Working on it... Russ On Sun, Nov 17, 2024 at 7:05 PM Xiao Li wrote: > Hi, Russell, > > > After reviewing the JIRAs, it seems that only SPARK-42856 is directly > relevant to GraphX. Whi