5 ms·
It's not immediately clear to me where this is superior to BigQuery authorized views: https://cloud.google.com/bigquery/docs/authorized-views#row-level-permiss
by scottfr 5y ago
It's not immediately clear to me where this is superior to BigQuery authorized views:
https://cloud.google.com/bigquery/docs/authorized-views#row-level-permissions https://cloud.google.com/bigquery/docs/authorized-views#row-...
The comparison in the source doc (https://cloud.google.com/bigquery/docs/row-level-security-intro#when_to_use_row-level_security_vs_other_methods https://cloud.google.com/bigquery/docs/row-level-security-in...) seems to list the same caveats for both methods.
- deleted 5y ago[deleted]
- SNosTrAnDbLe 5y agoI dont think its superior or inferior. Row level security is a different way to think about access control. I think of row level security as enforced on the table which is stronger as it will apply for any reads on the table. However, if you have authorized views then you can still create a different view of the same table without the access controls. You can probably use both to solve the problem and in some cases authorized views maybe the right choice and in some cases row level security will work.