Make it possible to apply a Filter or RLS (Row Level Security) on OneLake shortcuts.
For example:
We have a central workspace which holds data for the entire organization. We have a giant fact table with data for all departments in the organization.
We would like to create shortcuts from each department's workspace to the central fact table, but we would like each shortcut to only have access to that department's data.
So we need the ability to apply filter or RLS to the shortcut.
4 Comments
Agreed. Having the ability to govern what gets propagated via shortcuts would be a massive help and also work toward a better "OneCopy" approach to data in OneLake. In cases where you want certain lakehouses/workspaces to only house specific data, the only current option is to basically duplicate data into a lakehouse.
- Status added:New
- Same here, would love to see it in order to make OneLake Security Adoption happen
- Kevin_H
Advocate I
Today, one could add OneLake Security roles on the lakehouse (assuming it's a lakehouse) in the central workspace. When a user is accessing content in the departments' workspaces, via the shortcut, their identity can "flow" to the lakehouse in the central workspace, where OneLake Security (and its RLS) would be applied. Right? Wouldn't this solve it?
_
