[ https://issues.jboss.org/browse/TEIID-2327?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2327: --------------------------------------- While associating masks/filters on a per-role basis is conceptually good, the implementation may need tweaked. For instance the current approach to row based security is applied based upon the assigned roles each time a query is planned. In practice for any role other than an any-authenticated, this leads us to mark the plan as user specific. This is fine for result set caching, but will create a lot of prepared plans. One possibility would be to aggregate filters across all roles with appropriate conditionals on role assignment so that a single condition is applicable to all scenarios - the drawback being that this could lead to suboptimal plans if any one of the role conditions cannot be pushed - as they will be connected via or. Another option would be to add applicable roles to the determinism tracking. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira