[GitHub] [spark] aaronsteers removed a comment on issue #5617: [SPARK-7037] [CORE] Inconsistent behavior for non-spark config properties in spark-shell and spark-submit

[GitBox <gi...@apache.org>]

aaronsteers removed a comment on issue #5617: [SPARK-7037] [CORE] Inconsistent behavior for non-spark config properties in spark-shell and spark-submit
URL: https://github.com/apache/spark/pull/5617#issuecomment-565685945
 
 
   Is it expected that this error would print aws security keys to log files? Seems like a serious security concern.
   
   ```
   Warning: Ignoring non-spark config property: fs.s3a.access.key={full-access-key}
   Warning: Ignoring non-spark config property: fs.s3a.secret.key={full-secret-key}
   ```
   
   Could we not accomplish the same thing by printing the name of the key **without** the key's value?
   
   This might just be on my side, but my understanding is that I should be able to configure these via spark conf.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org