[ https://issues.jboss.org/browse/TEIID-2844?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2844: --------------------------------------- The approach here will be to handle this on the server side close to the AuthorizationValidationVisitor. The logic does support the concept of modifying the query as part of the authorization, so it should be straight-forward to remove the extra columns. However with the current logic it will inhibit plan and result set caching for modified queries - but that can be addressed later. Possibilities for enabling this feature include: a vdb property a connection property a server side configuration a system property I'm leaning toward using a vdb property and possibly a system property to control the system wide default behavior. -- 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