You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could not find useful information about this after some very long researching. Best I can find is that I create a policy to grant EXECUTE on foo.system.query schema function. However, there is no EXECUTE permission for schema functions as seen here.
I am using Trino 468 with Ranger 2.5.0 at the moment. This was not an issue with Trino 418 and Ranger 2.4.0. But I see that this has been added after 418.
We had to do a migration when upgrading Ranger and manually updated the service definition for Trino. So, the reason might be that there was an error with the migration but relevant sections look correct.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am having permission issues with
system.query
when using the Ranger plugin.When I ran queries like:
I get errors of the type:
I could not find useful information about this after some very long researching. Best I can find is that I create a policy to grant
EXECUTE
onfoo.system.query
schema function. However, there is noEXECUTE
permission for schema functions as seen here.I am using Trino 468 with Ranger 2.5.0 at the moment. This was not an issue with Trino 418 and Ranger 2.4.0. But I see that this has been added after 418.
We had to do a migration when upgrading Ranger and manually updated the service definition for Trino. So, the reason might be that there was an error with the migration but relevant sections look correct.
Is this a known issue? Are there any solutions?
Beta Was this translation helpful? Give feedback.
All reactions