[teiid-issues] [JBoss JIRA] (TEIID-5844) Dynamic into issues

[Steven Hawkins (Jira)]

     [ https://issues.redhat.com/browse/TEIID-5844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-5844:
----------------------------------
     Description: The documentation states that a temp table must be the target of a dynamic execute into, but there is nothing preventing that.  There is also the assumption that the insert must supply all columns and is positional - but that generally only makes sense if the temp table has not yet been defined.  If it already exists, then one could expect that the insert would happen based upon matching the column names - but it does not.  That needs to be clear in the code/docs.  (was: Anyone with the permission to create a temporary table can create a foreign temporary table.  From there we'll check the permissions on operations against the schema.  It would be nice to error out on the create temporary table if the user is not going to be sufficient permissioned to use it.  It's currently not the case, but if we ever have source level side effects from create foreign temp, then it becomes important to prevent the create as well.  )
    Story Points: 0.5
          Sprint: DV Sprint 63
         Summary: Dynamic into issues  (was: Schema level permissions are not checked proactively for foreign temporary tables)
        Priority: Major  (was: Minor)


In looking at the original issue, I saw a problem with the authorization check on dynamic into.  The original issue is probably too low of a priority to worry about - we'll add addition auth checks if/when there are create side effects.

> Dynamic into issues
> -------------------
>
>                 Key: TEIID-5844
>                 URL: https://issues.redhat.com/browse/TEIID-5844
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Major
>             Fix For: 14.0
>
>
> The documentation states that a temp table must be the target of a dynamic execute into, but there is nothing preventing that.  There is also the assumption that the insert must supply all columns and is positional - but that generally only makes sense if the temp table has not yet been defined.  If it already exists, then one could expect that the insert would happen based upon matching the column names - but it does not.  That needs to be clear in the code/docs.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)