[
https://jira.jboss.org/jira/browse/TEIID-1019?page=com.atlassian.jira.plu...
]
Michael Walker commented on TEIID-1019:
---------------------------------------
Yes, the cardinality is accurate. So the issue is with the estimation logic. I noticed
that the "estimated cardinality" was being set for some parts of the plan, but
not others. I uploaded the VDB and example queries to the JBEDSP ticket, which should
illustrate it.
In that VDB, if you open the mapping class for Style and add "OPTION NOCACHE
CIM.Style", you will get a validation error...perhaps this should be a separate
JIRA?
As for the cardinality, that makes sense. Do we have a JIRA to set 'unknnown' to a
different value?
Request ability to turn on/off Auto Staging tables
--------------------------------------------------
Key: TEIID-1019
URL:
https://jira.jboss.org/jira/browse/TEIID-1019
Project: Teiid
Issue Type: Feature Request
Components: Server, XML Planner/Processor
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Fix For: 7.0
Please add the ability to turn on/off Auto Staging tables. Setting the Cardinality to 0
is not always a workaround if the customer wants the cardinality set for better query
planning on other models.
--
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