[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2429:
----------------------------------------
We already established the fact that Designer 9.0.x currently does not support 8.10. The above comment does not give me any details as to why we can not do it?
> Teiid Designer do not compatible with Teiid 8.10
> ------------------------------------------------
>
> Key: TEIIDDES-2429
> URL: https://issues.jboss.org/browse/TEIIDDES-2429
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: 9.0
> Environment: Teiid 8.10.Beta2
> JBDS 8.0(https://devstudio.jboss.com/updates/8.0/integration-stack/)
> Reporter: Kylin Soong
> Priority: Critical
>
> Import Metadata from JDBC Data source through the following error:
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2215)
> Does this should be a feature request?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ]
Ramesh Reddy edited comment on TEIIDDES-2429 at 3/24/15 12:04 PM:
------------------------------------------------------------------
> Designer's teiid-client was built with Teiid 8.7 code so expecting it to work with a Teiid 8.10 server is pushing one's luck to say the least.
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.
> If the user chooses the 'default server version' to be Teiid 8.4 then ROLLUP will be invalid. If the user chooses the 'default server version' to be Teiid 8.5 then ROLLUP will be valid;
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.
> which is what Designer's teiid client does if the user has selected a 'default server version' less than Teiid 8.5. If more then valdation succeeds.
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 NOT 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.
was (Author: rareddy):
> Designer's teiid-client was built with Teiid 8.7 code so expecting it to work with a Teiid 8.10 server is pushing one's luck to say the least.
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.
> If the user chooses the 'default server version' to be Teiid 8.4 then ROLLUP will be invalid. If the user chooses the 'default server version' to be Teiid 8.5 then ROLLUP will be valid;
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.
> which is what Designer's teiid client does if the user has selected a 'default server version' less than Teiid 8.5. If more then valdation succeeds.
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.
> Teiid Designer do not compatible with Teiid 8.10
> ------------------------------------------------
>
> Key: TEIIDDES-2429
> URL: https://issues.jboss.org/browse/TEIIDDES-2429
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: 9.0
> Environment: Teiid 8.10.Beta2
> JBDS 8.0(https://devstudio.jboss.com/updates/8.0/integration-stack/)
> Reporter: Kylin Soong
> Priority: Critical
>
> Import Metadata from JDBC Data source through the following error:
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2215)
> Does this should be a feature request?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2429:
----------------------------------------
> Designer's teiid-client was built with Teiid 8.7 code so expecting it to work with a Teiid 8.10 server is pushing one's luck to say the least.
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.
> If the user chooses the 'default server version' to be Teiid 8.4 then ROLLUP will be invalid. If the user chooses the 'default server version' to be Teiid 8.5 then ROLLUP will be valid;
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.
> which is what Designer's teiid client does if the user has selected a 'default server version' less than Teiid 8.5. If more then valdation succeeds.
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.
> Teiid Designer do not compatible with Teiid 8.10
> ------------------------------------------------
>
> Key: TEIIDDES-2429
> URL: https://issues.jboss.org/browse/TEIIDDES-2429
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: 9.0
> Environment: Teiid 8.10.Beta2
> JBDS 8.0(https://devstudio.jboss.com/updates/8.0/integration-stack/)
> Reporter: Kylin Soong
> Priority: Critical
>
> Import Metadata from JDBC Data source through the following error:
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2215)
> Does this should be a feature request?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2429:
----------------------------------------
To shed light on Designer's support of Teiid versions.....
My understanding of the Teiid Server/runtime version support is that it's based on being able to consume artifacts from older versions as well as the latest. I'm guessing there are instances where older artifacts may not be "fully" compatible with newer Teiid runtimes, but I understand your goal is backward support.
Designer's requirement is to support the development and maintenance of artifacts for different Teiid target runtimes. This requirement exists so users can load older artifacts into their workspace, connect to a newer server version and if there are any particular changes in constructs/SQL or SQL validation that have changed, Designer will point out those issues and the user can fix them.
Designer couldn't do that if it only supported the latest version of Teiid. Supporting the move from Teiid 7.x to 8.x probably posed the largest challenge, but even Teiid 8.x minor releases have impacted SQL constructs and validation that needed to get tracked/addressed.
For Designer 9.1 we'll be trying to add an option to relax the version restriction for Teiid version so users can "disable" our basic version-support and proceed at their own risk.
As we move into our Komodo release, we'll hoping to drop specific support for older server versions because migration will entail converting old artifacts into the latest Teiid DDL/VDB structures.
> Teiid Designer do not compatible with Teiid 8.10
> ------------------------------------------------
>
> Key: TEIIDDES-2429
> URL: https://issues.jboss.org/browse/TEIIDDES-2429
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: 9.0
> Environment: Teiid 8.10.Beta2
> JBDS 8.0(https://devstudio.jboss.com/updates/8.0/integration-stack/)
> Reporter: Kylin Soong
> Priority: Critical
>
> Import Metadata from JDBC Data source through the following error:
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2215)
> Does this should be a feature request?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-2429.
---------------------------------------
Resolution: Won't Fix
To be explicit.
Designer 9.0.x does not support Teiid 8.10. It only has notional support up to Teiid 8.9 and tested support up to Teiid 8.7.
> Teiid Designer do not compatible with Teiid 8.10
> ------------------------------------------------
>
> Key: TEIIDDES-2429
> URL: https://issues.jboss.org/browse/TEIIDDES-2429
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: 9.0
> Environment: Teiid 8.10.Beta2
> JBDS 8.0(https://devstudio.jboss.com/updates/8.0/integration-stack/)
> Reporter: Kylin Soong
> Priority: Critical
>
> Import Metadata from JDBC Data source through the following error:
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2215)
> Does this should be a feature request?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-2429:
-------------------------------------------
[~rareddy]
You're right! Turns out that Designer does support the ".0" suffix (my mistake!). The error has occurred because Designer 9.0.x was only targeting Teiid versions up to 8.7 and in fact the Teiid runtime registry component of Designer only provided any kind of support up to Teiid 8.9 (since 8.10 had not even been released). Designer's teiid-client was built with Teiid 8.7 code so expecting it to work with a Teiid 8.10 server is pushing one's luck to say the least.
Some confusion over ROLLUP. Let me clarfiy:
* "I am not asking Designer with Teiid 8.4 client to support ROLLUP in Teiid 8.5 runtime" - good. Glad we agree. Except that Designer will not have a Teiid 8.4 client but in this case has a Teiid 8.7 client that can behave as a Teiid 8.4 client if that is the version of the server which is being targeted by the user. If the user chooses the 'default server version' to be Teiid 8.4 then ROLLUP will be invalid. If the user chooses the 'default server version' to be Teiid 8.5 then ROLLUP will be valid;
* "but support Teiid 8.4 metadata in the Teiid 8.5 runtime" - No problem. Its a Teiid 8.7 client so no issue there either;
* "If user does use, ROLLUP by all means fail saying Designer does not support it yet." - which is what Designer's teiid client does if the user has selected a 'default server version' less than Teiid 8.5. If more then valdation succeeds.
The point is that the requirements of Designer Teiid client are much broader than any single version of Teiid provides. Consequently, Teiid client libraries have not been simply bundled into Designer for a while now. Thus, despite demands it is essential that users need to use the appropriate version of Designer that has support for the version of Teiid server being modelled against.
> Teiid Designer do not compatible with Teiid 8.10
> ------------------------------------------------
>
> Key: TEIIDDES-2429
> URL: https://issues.jboss.org/browse/TEIIDDES-2429
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: 9.0
> Environment: Teiid 8.10.Beta2
> JBDS 8.0(https://devstudio.jboss.com/updates/8.0/integration-stack/)
> Reporter: Kylin Soong
> Priority: Critical
>
> Import Metadata from JDBC Data source through the following error:
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2215)
> Does this should be a feature request?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2429:
----------------------------------------
Teiid always released with "8.10.0-Final" kind name pattern, there is no change in the name. As per your ROLLUP comment, I am not asking Designer with Teiid 8.4 client to support ROLLUP in Teiid 8.5 runtime, but support Teiid 8.4 metadata in the Teiid 8.5 runtime. If user does use, ROLLUP by all means fail saying Designer does not support it yet.
> Teiid Designer do not compatible with Teiid 8.10
> ------------------------------------------------
>
> Key: TEIIDDES-2429
> URL: https://issues.jboss.org/browse/TEIIDDES-2429
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: 9.0
> Environment: Teiid 8.10.Beta2
> JBDS 8.0(https://devstudio.jboss.com/updates/8.0/integration-stack/)
> Reporter: Kylin Soong
> Priority: Critical
>
> Import Metadata from JDBC Data source through the following error:
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2215)
> Does this should be a feature request?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Paul Richardson (JIRA)
[ 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.
> Teiid Designer do not compatible with Teiid 8.10
> ------------------------------------------------
>
> Key: TEIIDDES-2429
> URL: https://issues.jboss.org/browse/TEIIDDES-2429
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: 9.0
> Environment: Teiid 8.10.Beta2
> JBDS 8.0(https://devstudio.jboss.com/updates/8.0/integration-stack/)
> Reporter: Kylin Soong
> Priority: Critical
>
> Import Metadata from JDBC Data source through the following error:
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2215)
> Does this should be a feature request?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ]
Ramesh Reddy updated TEIIDDES-2429:
-----------------------------------
Issue Type: Bug (was: Feature Request)
Priority: Critical (was: Major)
I have suggested many times that Designer tooling either need to lock step in releases with Teiid runtime or provide workable solutions with later releases. Teiid metadata and client code are always forward compatible in a given major release cycle, like 7.x, 8.x.
So, it does not matter what Teiid libraries that Designer is using for metadata validation and preview functionality, they are expected to work with later releases of Teiid in the same major revision. If Designer team is seeing something different, Teiid needs to know.
Not doing this we are just going to alienate/aggravate more of the community participation and adoption. So, please fix this!
> Teiid Designer do not compatible with Teiid 8.10
> ------------------------------------------------
>
> Key: TEIIDDES-2429
> URL: https://issues.jboss.org/browse/TEIIDDES-2429
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: 9.0
> Environment: Teiid 8.10.Beta2
> JBDS 8.0(https://devstudio.jboss.com/updates/8.0/integration-stack/)
> Reporter: Kylin Soong
> Priority: Critical
>
> Import Metadata from JDBC Data source through the following error:
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2215)
> Does this should be a feature request?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years