01-04-2016 02:05 AM
I would like tyo apply row Level security on KUDU tables. I checked the documentations of recordServices it sounds to me that the unique solution would be to create dedicated view per Role.
Am I right? Or is the feature really implemented in recordServices?
01-05-2016 01:15 PM
The features you mentioned are being implemented in coming months, in this order:
1) RecordService support for Kudu
2) RecordService/Sentry support for row-level permissions
You are correct that once the first item above is completed, you could create separate views that include different rows from a table - then use Sentry to assign permissions to separate roles for each view. RecordService will enforce these permissions. Once the second item is completed, there could be a single view which returns different sets of rows depending on the role of the user performing the query.