[JBoss JIRA] (TEIIDDES-2459) Enabling minimal support for as-yet unsupported Teiid versions
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2459?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2459:
----------------------------------------
Committed change to 9.0.x to fix the 1) issue above. https://github.com/Teiid-Designer/teiid-designer/commit/ac018b6354f21f1cf...
The second 2) issue is of lesser importance. I think we should log another issue to "relax" the check to maybe ignore the patch version?
> Enabling minimal support for as-yet unsupported Teiid versions
> --------------------------------------------------------------
>
> Key: TEIIDDES-2459
> URL: https://issues.jboss.org/browse/TEIIDDES-2459
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Teiid Integration
> Affects Versions: 9.0.2
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
>
> Since there is only one teiid-client plugin which is responsible for all versions of teiid instance support, there is no longer any point in specifying versions that the plugin supports.
> Thus, update the plugin to establish levels of support for versions of Teiid, ie. no support, full support and works-but-no-support. This should allow versions of Teiid that have not yet been fully integrated and tested to be connected to by the client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2405.
------------------------------------
Verified with Teiid Designer 9.0.2 Beta1
> Teiid Importer *MUST* not require class-name property working with Teiid Sources
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2405
> URL: https://issues.jboss.org/browse/TEIIDDES-2405
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Priority: Critical
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: cassandra-ra.txt
>
>
> When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source
> {code}
> {"managedconnectionfactory-class" => {
> "type" => STRING,
> "display" => "managedconnectionfactory-class",
> "read-only" => "true",
> "advanced" => "true",
> "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory"
> }},
> {code}
> That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2459) Enabling minimal support for as-yet unsupported Teiid versions
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2459?page=com.atlassian.jira.plu... ]
Andrej Šmigala reopened TEIIDDES-2459:
--------------------------------------
The implementation of this is incorrect:
I defined two servers, DV 6.1 GA (with Teiid 8.7.1) and Teiid 8.10.
Switching the default server between these two works in exactly the opposite way than is expected, due to two separate issues:
1) switching to Teiid 8.10 does _not_ show the unsupported server version message
This is due to the way version comparison is done in TeiidServerVersion here: https://github.com/Teiid-Designer/teiid-designer/blob/9.0.x/plugins/org.t...
On line 340, the minor components are compared using String.compareTo, which compares the strings lexicographically. "10" therefore compares as less than "7", and the version 8.10.1 is considered lower than the default 8.7.0.
2) switching to Teiid 8.7.1 _does_ show the unsupported server version message
This is because the default server version is set to TEIID_8_7, which is defined as TEIID_8_7(EIGHT + DOT + SEVEN + DOT + ZERO), i.e. 8.7.0.
This of course compares as greater than the default 8.7.0.
> Enabling minimal support for as-yet unsupported Teiid versions
> --------------------------------------------------------------
>
> Key: TEIIDDES-2459
> URL: https://issues.jboss.org/browse/TEIIDDES-2459
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Teiid Integration
> Affects Versions: 9.0.2
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
>
> Since there is only one teiid-client plugin which is responsible for all versions of teiid instance support, there is no longer any point in specifying versions that the plugin supports.
> Thus, update the plugin to establish levels of support for versions of Teiid, ie. no support, full support and works-but-no-support. This should allow versions of Teiid that have not yet been fully integrated and tested to be connected to by the client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2512) Problems with starting DV server from Teiid Designer 9.0.2.Beta1
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2512?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2512:
--------------------------------------
Assignee: Paul Richardson
> Problems with starting DV server from Teiid Designer 9.0.2.Beta1
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2512
> URL: https://issues.jboss.org/browse/TEIIDDES-2512
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.2 Beta1
> Reporter: Matus Makovy
> Assignee: Paul Richardson
> Priority: Minor
> Fix For: 9.1, 9.0.2
>
> Attachments: Screen Shot 2015-05-06 at 2.36.38 PM.png
>
>
> When I try to start DV server from JBDS it starts normaly, but following exception occures (screenshot attached) :
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-children-names" for undefined. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available".
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:342)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.tryConnecting(TeiidParentServerListener.java:208)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.run(TeiidParentServerListener.java:177)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-children-names" for undefined. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available".
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:333)
> ... 9 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2536) No connection to Teiid instance after starting DV from JBDS - refresh needed
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2536?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2536:
--------------------------------------
Assignee: Paul Richardson
> No connection to Teiid instance after starting DV from JBDS - refresh needed
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-2536
> URL: https://issues.jboss.org/browse/TEIIDDES-2536
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.2 Beta1
> Reporter: Matus Makovy
> Assignee: Paul Richardson
> Fix For: 9.1, 9.0.2
>
> Attachments: Screen Shot 2015-05-20 at 9.40.55 AM.png, Screen Shot 2015-05-20 at 9.41.04 AM.png
>
>
> When you start DV server from JBDS there is no connection established to Teiid instance. You have to refresh server or Teiid Instance. Sometimes it is sufficient to expand particular server node in Servers view.
> I think this issue is releated to TEIIDDES-2512
> Screenshots attached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2512) Problems with starting DV server from Teiid Designer 9.0.2.Beta1
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2512?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2512:
-----------------------------------
Fix Version/s: 9.1
9.0.2
> Problems with starting DV server from Teiid Designer 9.0.2.Beta1
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2512
> URL: https://issues.jboss.org/browse/TEIIDDES-2512
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.2 Beta1
> Reporter: Matus Makovy
> Priority: Minor
> Fix For: 9.1, 9.0.2
>
> Attachments: Screen Shot 2015-05-06 at 2.36.38 PM.png
>
>
> When I try to start DV server from JBDS it starts normaly, but following exception occures (screenshot attached) :
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-children-names" for undefined. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available".
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:342)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.tryConnecting(TeiidParentServerListener.java:208)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.run(TeiidParentServerListener.java:177)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-children-names" for undefined. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available".
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:333)
> ... 9 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months