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

[Steven Hawkins (JIRA)]

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

Steven Hawkins resolved TEIID-189.
----------------------------------

    Fix Version/s: 7.2
                       (was: 7.3)
       Resolution: Partially Completed


For now cardinality is enough.  Will probably address other stats gathering as part of the runtime costing issue.

> Temp tables should maintain their costing metadata
> --------------------------------------------------
>
>                 Key: TEIID-189
>                 URL: https://jira.jboss.org/browse/TEIID-189
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine
>    Affects Versions: 8.x
>            Reporter: Steven Hawkins
>            Priority: Optional
>             Fix For: 7.2
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira