moelhoussein opened a new issue, #7230:
URL: https://github.com/apache/kyuubi/issues/7230

   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   
   
   ### Search before asking
   
   - [x] I have searched in the 
[issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Describe the bug
   
   For MongoDB, the table extractor fails to produce meaningful (database, 
table) identifiers. It relies on `DataSourceV2Relation.identifier` or 
`table.name`, which are empty, path-like, or non-semantic for these connectors. 
As a result, Ranger resources are misidentified and policies do not match.
   
   
   DataSource V2 connectors encode logical identifiers in `table.properties`, 
not in `identifier/table.name`. The extractor didn’t read connector-specific 
properties.
   
   ### Affects Version(s)
   
   master
   
   ### Kyuubi Server Log Output
   
   ```logtalk
   N/A
   ```
   
   ### Kyuubi Engine Log Output
   
   ```logtalk
   Exception in thread "main" 
org.apache.kyuubi.plugin.spark.authz.AccessControlException: Permission denied: 
user [JOB-USER] does not have [update] privilege on [MongoTable()]
   ```
   
   ### Kyuubi Server Configurations
   
   ```yaml
   
   ```
   
   ### Kyuubi Engine Configurations
   
   ```yaml
   
   ```
   
   ### Additional context
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes. I would be willing to submit a PR with guidance from the Kyuubi 
community to fix.
   - [ ] No. I cannot submit a PR at this time.


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