[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-2429: ------------------------------------------- [~rareddy] While it is excellent that you are contributing so promptly to this discussion, I would advise discussing your issues with the Designer team prior to commenting, in order to be fully apprised of all relevant information. The issue in question is most likely due to the extra ".0" suffix of the teiid version, which does not seem to occur on teiid releases (maybe you could verify why that is there). The teiid-runtime client loaded into Designer 9.0.x is tested compatible to version 8.7.x back to version 7.7.x. Unlike Teiid, Designer has to not only cross major version boundaries of Teiid but also ensure that query parsing/resolving/validating passes/fails across minor Teiid versions as well. To illustrate the latter point: * The keyword ROLLUP was introduced in Teiid 8.5 (a minor version). To support this keyword, it was included in Designer's teiid-runtime client. However, support could not 'just' be added since users running Teiid 8.4 and below would not want the keyword to validate successfully in Designer then deploy their vdb and have it fail on the server. Therefore, the version of teiid server being used is injected into the parser/resolver/validator and checked against when a keyword like this is being parsed, ie. parser fails for Teiid 8.4 and succeeds for Teiid 8.5+. I hope this illustrates that it DOES matter what Teiid libraries Designer is using for metadata validation. This will be triaged and fixed in the normal course of bug fixing. -- This message was sent by Atlassian JIRA (v6.3.11#6341)