kongjiexin888-source opened a new pull request, #7439:
URL: https://github.com/apache/kyuubi/pull/7439

   ### Why are the changes needed?
   The built-in JSON event logger currently creates event log directories and 
actively sets permissions on directories and log files.
   
   This default behavior is useful for the built-in permission model, but it 
can conflict with deployments where access control is managed by Apache Ranger, 
inherited HDFS ACLs, or other external authorization systems. In those 
environments, an engine user may have permission to create and write event 
logs, while still not being allowed to call `setPermission` on the target path.
   
   This patch adds `kyuubi.event.json.log.manage.permissions.enabled`, 
defaulting to `true`, to keep the existing behavior unchanged. When set to 
`false`, the JSON event logger no longer actively manages directory or file 
permissions, leaving access control to Ranger, HDFS ACLs, filesystem defaults, 
or other external permission systems.
   
   This helps multi-tenant Kyuubi deployments use a shared JSON event log root 
without requiring
   each engine user to own or chmod the target HDFS path.
   
   
   ### How was this patch tested?
   - [x] Added tests for default JSON event log file permission management.
   - [x] Added tests for writing JSON event logs when permission management is 
disabled.
   - [x] Ran:
   ```bash
   build/mvn -pl kyuubi-events -am 
-DwildcardSuites=org.apache.kyuubi.events.handler.JsonLoggingEventHandlerSuite 
test
   ```
   
   ### Was this patch authored or co-authored using generative AI tooling?
   This patch was prepared with assistance from OpenAI Codex; the contributor 
reviewed and validated the changes.
   
   


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