[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2429: ---------------------------------------- That is misconception, Let's dig in. What did you see that is changed? In Teiid 8.10, we still support Teiid 8.7 specific metadata, Admin API, JDBC Connection. If there are any metadata changes, they are designed to be backwards compatible (99% of time). What is the issue failing to support this? I really would like to know, so that we can fix this. seems like there is design smell for me, the version of compliance and version of runtime are two separate constructs, they need to be treated as such. The compliance version can be fixed version like 8.7, based on the Teiid libraries used. Runtime is version that Designer connected to is entirely separate. Do not try to mix or treat one for the other. What Designer does in case is renders itself useless *completely* for the user, if it is not connected to the mandated Teiid runtime version. See example here TEIIDDES-2446. Which IMO is bad behavior. In my comment I suggested support ROLLUP, but if somebody is doing "select * from foo" by all means we need to support that. Please do not close this with Won't Fix, the issue is not going to away because of it, we need to find a resolution to this. -- This message was sent by Atlassian JIRA (v6.3.11#6341)