LevisNgigi commented on issue #35158: URL: https://github.com/apache/superset/issues/35158#issuecomment-3341428867
> I didn't see if this was mentioned anywhere, but Superset actually had an experimental native filter precisely for this purpose, but which was later removed due to poor maintenance. See the PR from 5 years ago that added this: [#14217](https://github.com/apache/superset/pull/14217) . > > One issue that comes to mind for me is security implications of being able to add granularity to charts. There may be situations where a dashboard shows highly aggregated data that's referenced from tables containing sensitive data that should only be aggregated to a certain level. Providing an option to dynamically group data further could lead to situations where the data that's displayed is so granular that it singles out data that should not have been possible. > > Not necessarily a blocker, but I think it could at a minimum be a good idea to be able to specify which columns are allowed for grouping, especially for very wide tables where there's only a few columns that are relevant for dashboard consumers. @villebro Thank you for the input. Our current implementation groups columns that are exposed in the dataset’s metadata.Can the dataset owner specify which columns are accessible for dashboard consumers? Would need more input on this on defining sensible defaults like always allow high-level dimensions (region, product line) but never allow user-identifying fields (email, phone)? -- 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]
