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
Is your feature request related to a problem or challenge?
The current problem is that I need to have the ability to do row level security and column level security and column mask and currently I can’t do that.
Trino allows that using their opa plugin and authorization in the Trino engine.
Describe the solution you'd like
Please support and allow making authorization in datafusion making it a candidate to replace Trino in cases where rls authorization logic is needed.
So every query sent to DataFusion will be parsed and raise an authorization process checking user access and applying rls and column mask if needed.
Describe alternatives you've considered
Use Trino as a query engine
Additional context
The main usecase is authorization over iceberg based datalake
The text was updated successfully, but these errors were encountered:
In catalog you can have only table level authorization(you have access to a table or not) but you cant have row level as it required to do some compute on the data(filter it for row level or masking the data for column mask .etc)
the best case and there where things are going the catalog will return the authorization logic and the compute engine(need to be a trusted compute engine) will do the authorization logic based on the returned logic from the catalog.
But still the engine will need to have a way to do the authorization logic.
Is your feature request related to a problem or challenge?
The current problem is that I need to have the ability to do row level security and column level security and column mask and currently I can’t do that.
Trino allows that using their opa plugin and authorization in the Trino engine.
Describe the solution you'd like
Please support and allow making authorization in datafusion making it a candidate to replace Trino in cases where rls authorization logic is needed.
So every query sent to DataFusion will be parsed and raise an authorization process checking user access and applying rls and column mask if needed.
Describe alternatives you've considered
Use Trino as a query engine
Additional context
The main usecase is authorization over iceberg based datalake
The text was updated successfully, but these errors were encountered: