Repository navigation
TEZ-4756: DAGUtils: configuration handling improvements - #539
abstractdog wants to merge 3 commits into
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The new unit test includes credential-like strings that can trigger secret-scanning and it should be adjusted to use safe placeholders and more reliably exercise default redaction behavior.
Get a fresh assessment by requesting another Copilot review.
Pull request overview
Improves how Tez publishes AM configuration data to YARN Timeline/ATS by redacting sensitive configuration values (based on Hadoop’s sensitive-key patterns) before building the ATS configuration map, and adds a unit test covering redaction behavior.
Changes:
- Route all configuration values through Hadoop
ConfigRedactorinDAGUtils.convertConfigurationToATSMap. - Add a unit test verifying sensitive keys are masked and non-sensitive keys remain unchanged.
File summaries
| File | Description |
|---|---|
| tez-dag/src/main/java/org/apache/tez/dag/history/utils/DAGUtils.java | Redacts configuration values via ConfigRedactor before publishing to ATS. |
| tez-dag/src/test/java/org/apache/tez/dag/history/utils/TestDAGUtils.java | Adds a unit test validating redaction behavior for sensitive configuration keys. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
💔 -1 overall
This message was automatically generated. |
Route each key/value pair through Hadoop's ConfigRedactor when building the ATS configuration map, so values matching the cluster's configured sensitive-key pattern are masked in the map published to Timeline. Adds a unit test. Co-Authored-By: Claude Code <noreply@anthropic.com>
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
| // core-default.xml and misses fs.s3a.session.token. | ||
| Configuration conf = new Configuration(); | ||
| conf.set("tez.am.dag.scheduler.class", | ||
| "org.apache.tez.dag.app.dag.impl.DAGSchedulerNaturalOrder"); |
There was a problem hiding this comment.
can we rather than hardcoding, using the Class.getName() and for the configs as well, the Config variables
|
🎊 +1 overall
This message was automatically generated. |
Route each key/value pair through Hadoop's ConfigRedactor when building the ATS configuration map, so values matching the cluster's configured sensitive-key pattern are masked in the map published to Timeline. Adds a unit test.