[teiid-issues] [JBoss JIRA] Updated: (TEIID-189) Temp tables should maintain their costing metadata

[Ramesh Reddy (JIRA)]

     [ https://jira.jboss.org/jira/browse/TEIID-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy updated TEIID-189:
-------------------------------

          Component/s: Query Engine
        Fix Version/s: 6.x
    Affects Version/s: 6.x


> Temp tables should maintain their costing metadata
> --------------------------------------------------
>
>                 Key: TEIID-189
>                 URL: https://jira.jboss.org/jira/browse/TEIID-189
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine
>    Affects Versions: 6.x
>            Reporter: Steven Hawkins
>            Priority: Optional
>             Fix For: 6.x
>
>
> Defect Tracker #24522: Temp table cardinality is currently only used for staging tables.  It would also be generally useful for ad hoc queries to have the TempTableStoreImpl maintain the cardinality of the tables.  Other costing information could actually be incorrect now (such as column min/max) depending upon what has been selected into a temp table.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira