shenrie commented on PR #8699: URL: https://github.com/apache/superset/pull/8699#issuecomment-1133469680
@altef A very useful feature, so thank you for implementing. I do have a question that I am confused about. The documentation and parts of the code reference "table and roles", however, in the UI it seems that it is not actually a database table that needs to be configured in the RLS, but actually a dataset. Is that a true or am I misunderstanding? The reason that I ask is in a scenario where I have a dozen different dashboards that use their own unique datasets, but which all include the same database table "abc" as part of their query, I would like the same RLS rule to apply to all of these dashboards, it would be great if I could specify the table "abc" in the rule, since that single table is common across all datasets. However, it would seem from my review of the UI/code that it is not the actual database table name that is defined in the RLS rule, but that all dozen datasets would have to be specified, which is not very scalable. Am I understanding this feature correctly? Or is there some other way to do what I would like to do by specify a single common table that is used within multiple dashboard datasets to ensure the RLS is enforced across all of them? Thank you in advance. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
