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

   ### 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
   
   Kyuubi Spark Authz is connected to ranger1.2.0 and configured with relevant 
policies
   
![image](https://github.com/apache/kyuubi/assets/18652779/827af68b-3d79-4681-b0cb-95fe3b3bcff0)
   
   This policy can be displayed normally on the spark-sql command line
   
![image](https://github.com/apache/kyuubi/assets/18652779/14f60828-d999-42f2-b9cf-0ca9315f39a6)
   
   However, through access in kyuubi, the beeline/ldap method returns empty,the 
select specific strategy table can query data normally
   <img width="890" alt="2ed9ba82b6dd225421e5359192c8a98" 
src="https://github.com/apache/kyuubi/assets/18652779/cd530dba-7fa5-4a8b-87e5-eebd7574c305";>
   
   
   
   ### Affects Version(s)
   
   1.8.0
   
   ### Kyuubi Server Log Output
   
   ```logtalk
   no
   ```
   
   
   ### Kyuubi Engine Log Output
   
   ```logtalk
   no
   ```
   
   
   ### Kyuubi Server Configurations
   
   ```yaml
   no
   ```
   
   
   ### Kyuubi Engine Configurations
   
   ```yaml
   no
   ```
   
   
   ### Additional context
   
   no
   
   ### Are you willing to submit PR?
   
   - [ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi 
community to fix.
   - [X] 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