dongjoon-hyun opened a new pull request, #58911:
URL: https://github.com/apache/spark/pull/58911

   ### What changes were proposed in this pull request?
   
   This PR aims to redact the exit exception annotation, 
`spark.exit-exception`, with `spark.redaction.string.regex` when 
`spark.kubernetes.driver.annotateExitException` is enabled.
   
   In addition, this PR documents the following.
   - The annotation is visible to anyone who can get the driver pod.
   - `spark.redaction.string.regex` is used for the exit exception annotation 
on Kubernetes.
   
   ### Why are the changes needed?
   
   `spark.kubernetes.driver.annotateExitException` (SPARK-53335) stores the 
stringified exit exception into the driver pod annotation without any 
redaction. Since an exception message may contain sensitive information like 
JDBC URLs, it is visible to anyone who can get the driver pod.
   
   `spark.redaction.string.regex` is the existing configuration to redact the 
strings produced by Spark, like the output of SQL explain commands. This PR 
reuses it so that users can hide the sensitive parts of the exit exception 
without a new configuration.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No behavior change by default because `spark.redaction.string.regex` has no 
default value. If a user sets `spark.redaction.string.regex`, the matching 
parts of the `spark.exit-exception` annotation are replaced with 
`*********(redacted)`.
   
   ### How was this patch tested?
   
   Pass the CIs with the newly added test case.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Opus 5


-- 
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]

Reply via email to