bjornjorgensen commented on pull request #35614: URL: https://github.com/apache/spark/pull/35614#issuecomment-1048178536
Thank you @dongjoon-hyun The problem today is that many people have a strong focus on data security. And when they - the user or the data security department of organizations see software with known security holes, then uncertainties arise. I agree with you that it takes an incredible amount of time for this security hole to be exploited in spark. But let's remove the doubt. And as long as our existing tests pass, I do not see the reason why we should stop either. I'm a little unsure what you mean by "Could you describe as a normal test dependency update instead of those false alarms, please?" I have now changed the title of the PR. If this is what you were thinking? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
