0AyanamiRei opened a new pull request, #65629:
URL: https://github.com/apache/doris/pull/65629

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: #64786
   
   Problem Summary: Backport Kafka routine-load sensitive-property masking from 
#64786 to `branch-4.1`. The display paths for `SHOW ROUTINE LOAD`, `SHOW CREATE 
ROUTINE LOAD`, and `information_schema.routine_load_jobs` mask credentials 
while the internal Kafka client properties remain unchanged.
   
   Source merge commit: `c4ddfbaa66a6039a0383fd3fa1fb8c549bfa4381`.
   
   ### Conflict resolution
   
   - `branch-4.1` does not contain Kinesis routine load. Kept 
`KinesisRoutineLoadJob`, its unit test, and its regression suite absent instead 
of resurrecting a component unavailable on the target branch.
   - Preserved the branch's JMockit-based `KafkaRoutineLoadJobTest` and 
inserted only the source PR's sensitive-property masking test.
   - Replaced master's `DatasourcePrintableMap.SENSITIVE_KEY` with the 
equivalent `PrintableMap.SENSITIVE_KEY` registry available on branch-4.1.
   - Retained the branch's existing Kafka configuration constants for SASL JAAS 
and AWS access-key matching.
   - The Kafka regression test merged against the target suite without 
additional semantic changes.
   
   ### Release note
   
   Mask sensitive Kafka routine load custom properties in metadata display 
output.
   
   ### Check List (For Author)
   
   - Test: No need to test (one-time Agent conflict-resolution workflow; build 
and test execution were intentionally excluded)
       - `git diff HEAD^ HEAD --check`
       - Verified no conflict markers or unmerged index entries remain
   - Behavior changed: Yes (Kafka routine load credentials are masked in 
external metadata displays)
   - Does this need documentation: No
   


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