[ https://jira.jboss.org/jira/browse/TEIID-1019?page=com.atlassian.jira.plu... ] Michael Walker commented on TEIID-1019: --------------------------------------- One problem is that we are choosing to use autostaging when we shouldn't be doing so. We are getting an inefficient query plan that does not push down any criteria, and stages an entire table containing millions of rows, even though we have the opportunity to pushdown criteria and retrieve just 1-2 rows. Setting all source system table cardinality to 0 seems to give us the correct query plan, but we lose costing info for other queries. I have a customer-specific example VDB that might help illustrate the problem. I will open a separate JIRA in JBEDSP. This way, I can attache the customer-specific VDB. Also, we can ensure the fix gets into JBEDSP, not just Teiid. Just to clarify, we're talking about the cardinality of source system tables (in RDBMSes), not the mapping classes themselves. About the "option nocache" -- are you saying that you can add this in the XML document model transformation? I tried it, but Designer says it's invalid to do it against anything that isn't a materialized view, and won't validate it. Perhaps you're suggesting something different here, let me know. -- 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

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

[ https://jira.jboss.org/jira/browse/TEIID-1019?page=com.atlassian.jira.plu... ] Michael Walker commented on TEIID-1019: --------------------------------------- The GSS case was closed, since we have a workaround and don't need a patch at this point. I did create a JBEDSP JIRA for it: https://jira.jboss.org/jira/browse/JBEDSP-1204 the VDB and example query can be found there. I talked with Steve Jacobs earlier this month about JIRA process, and it's my understanding that we should continue to log defects in JBEDSP to ensure they make it into the current enterprise product. Apparently, there is a process in place to copy JBEDSP defects into Teiid (assuming they are also relevant for Teiid). In this case, we did the opposite (Teiid first, JBEDSP second), but the effect is the same. So, for the validation issue, I will create a separate issue in JBEDSP now, and let the standard process get it into Teiid as well. -- 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

[ https://jira.jboss.org/jira/browse/TEIID-1019?page=com.atlassian.jira.plu... ] Steven Hawkins resolved TEIID-1019. ----------------------------------- Resolution: Incomplete Description Resolving as incomplete description. This will be resolved as the individual issues that it's spawned. -- 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