Github user maropu commented on the issue:
https://github.com/apache/spark/pull/21514
Is this only the place where we need to hide the password? e.g., how about
logging about properties in
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/21514
Have you tried the config "spark.redaction.regex" ?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For
Github user tooptoop4 commented on the issue:
https://github.com/apache/spark/pull/21514
@dbtsai
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21514
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user tooptoop4 commented on the issue:
https://github.com/apache/spark/pull/21514
I just went through the process of getting 'security approval' in my
organisation to use Spark in Production. They ran a Qualsys Vulnerability
Assessment scanner that among other things picked up
Github user pjfanning commented on the issue:
https://github.com/apache/spark/pull/21514
Instead of filtering out the passwords, would it be more useful to blank
the passwords or replace them with `**` in the output?
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21514
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21514
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
