[teiid-issues] [JBoss JIRA] (TEIID-2507) Better handling of user scoped lookups

Wed May 29 10:41:54 EDT 2013

    [ https://issues.jboss.org/browse/TEIID-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777898#comment-12777898 ] 

Steven Hawkins commented on TEIID-2507:
---------------------------------------

Given the current implementation and intention of the lookup function, I don't think that we want to alter the current approach.  The docs will be updated that lookup against views (or tables that have source row-level security) may not return the expected results for multiple users.

I'll also add an info log to the global matview load logic to let admins know if the materialized table is not appropriately deterministic.

Other possibilities include:
-taking the notion of a virtual private database further and allowing for user scoped vdb such that there is no issue with cache segregation.
-generally allowing for session scoped mat views (although a session scoped lookup would require an additional parameter to the lookup function), since it is relatively easy to extend the matview/with logic to allow for tables to be created in the session, rather than global, store.
-updating the matview logic to be user aware - however this greatly complicates the considerations of, storage, loading, and refreshing which is why it seems best not to pursue this approach.

> Better handling of user scoped lookups
> --------------------------------------
>
>                 Key: TEIID-2507
>                 URL: https://issues.jboss.org/browse/TEIID-2507
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.4
>
>
> With the inclusion of column and row security logic, it's more likely that lookups can produce user specific results.  The current logic however treats lookups as always globally scoped.

--
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