February 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2070) add search/replace to the Teiid Designer-->search transformations feature

by Tom Johnston (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2070?page=com.atlassian.jira.plu... ] Tom Johnston commented on TEIIDDES-2070: ---------------------------------------- Quite often when one needs to search/sift through existing transformations there is a resulting 'change' so the ability to search/replace portions of transformation queries en mass would be a great addition. > add search/replace to the Teiid Designer-->search transformations feature > ------------------------------------------------------------------------- > > Key: TEIIDDES-2070 > URL: https://issues.jboss.org/browse/TEIIDDES-2070 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Tom Johnston > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2070) add search/replace to the Teiid Designer-->search transformations feature

by Tom Johnston (JIRA)

Tom Johnston created TEIIDDES-2070: -------------------------------------- Summary: add search/replace to the Teiid Designer-->search transformations feature Key: TEIIDDES-2070 URL: https://issues.jboss.org/browse/TEIIDDES-2070 Project: Teiid Designer Issue Type: Feature Request Reporter: Tom Johnston -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1798) When selecting REST:CHARSET of UTF-8, designer halts

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1798?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1798: ----------------------------------------- linked JIRA > When selecting REST:CHARSET of UTF-8, designer halts > ---------------------------------------------------- > > Key: TEIIDDES-1798 > URL: https://issues.jboss.org/browse/TEIIDDES-1798 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Attachments: Sample.vdb > > > When building a rest procedure and selecting REST:CHARSET of UTF-8, designer halts. On the mac, get a continuous spinning wheel. It still has not stopped by the time I've completed writing this jira. > The second time having to kill JBDS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1798) When selecting REST:CHARSET of UTF-8, designer halts

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1798?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1798: ----------------------------------------- I wonder if this may be related to the linked JIRA (which I just fixed). We should have a mac user retest when a build is available > When selecting REST:CHARSET of UTF-8, designer halts > ---------------------------------------------------- > > Key: TEIIDDES-1798 > URL: https://issues.jboss.org/browse/TEIIDDES-1798 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Attachments: Sample.vdb > > > When building a rest procedure and selecting REST:CHARSET of UTF-8, designer halts. On the mac, get a continuous spinning wheel. It still has not stopped by the time I've completed writing this jira. > The second time having to kill JBDS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2048) TEIID70026 RAR file name supplied on operation is wrong or no such RAR file is currently deployed.

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2048?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-2048: ----------------------------------------- We'll need some more information about your scenario in order to determine. What were you doing in Designer when the problem occurred? Can you add and connect to the sources one-by-one to determine which is causing the issue? Also it might be helpful if you could attach a ModelProjectSet and the connection profile details. > TEIID70026 RAR file name supplied on operation is wrong or no such RAR file is currently deployed. > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2048 > URL: https://issues.jboss.org/browse/TEIIDDES-2048 > Project: Teiid Designer > Issue Type: Bug > Environment: Windows 7 64 bit,ram 4gb,jdk 1.6 update 31 > Reporter: Pachaimuthu S > Assignee: Mark Drilling > Priority: Critical > > Dear sir/madam, > After installed Data Virtualization v 6 GA i tried to connect DB2 10.1,mysql 5.1 and mssql server 2008 database i was getting error message: > TEIID70026 RAR file name supplied on operation is wrong or no such RAR file is currently deployed. > at org.teiid.adminapi.AdminFactory$AdminImpl$BuildPropertyDefinitions.onFailure(AdminFactory.java:1191) > at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1475) > at org.teiid.adminapi.AdminFactory$AdminImpl.getTemplatePropertyDefinitions(AdminFactory.java:1156) > at org.teiid84.runtime.ExecutionAdmin.refreshTranslators(ExecutionAdmin.java:659) > at org.teiid84.runtime.ExecutionAdmin.refresh(ExecutionAdmin.java:618) > at org.teiid84.runtime.ExecutionAdmin.connect(ExecutionAdmin.java:607) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:192) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:221) > at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:165) > at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125) > at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742) > at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143) > at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:210) > at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:100) > at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.handleAlreadyStartedScenario(AbstractJBossStartLaunchConfiguration.java:132) > at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.preLaunchCheck(AbstractJBossStartLaunchConfiguration.java:103) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7StartLaunchDelegate.preLaunchCheck(LocalJBoss7StartLaunchDelegate.java:39) > at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:67) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:813) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:700) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3537) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3473) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2048) TEIID70026 RAR file name supplied on operation is wrong or no such RAR file is currently deployed.

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2048?page=com.atlassian.jira.plu... ] Mark Drilling reassigned TEIIDDES-2048: --------------------------------------- Assignee: Mark Drilling > TEIID70026 RAR file name supplied on operation is wrong or no such RAR file is currently deployed. > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2048 > URL: https://issues.jboss.org/browse/TEIIDDES-2048 > Project: Teiid Designer > Issue Type: Bug > Environment: Windows 7 64 bit,ram 4gb,jdk 1.6 update 31 > Reporter: Pachaimuthu S > Assignee: Mark Drilling > Priority: Critical > > Dear sir/madam, > After installed Data Virtualization v 6 GA i tried to connect DB2 10.1,mysql 5.1 and mssql server 2008 database i was getting error message: > TEIID70026 RAR file name supplied on operation is wrong or no such RAR file is currently deployed. > at org.teiid.adminapi.AdminFactory$AdminImpl$BuildPropertyDefinitions.onFailure(AdminFactory.java:1191) > at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1475) > at org.teiid.adminapi.AdminFactory$AdminImpl.getTemplatePropertyDefinitions(AdminFactory.java:1156) > at org.teiid84.runtime.ExecutionAdmin.refreshTranslators(ExecutionAdmin.java:659) > at org.teiid84.runtime.ExecutionAdmin.refresh(ExecutionAdmin.java:618) > at org.teiid84.runtime.ExecutionAdmin.connect(ExecutionAdmin.java:607) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:192) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:221) > at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:165) > at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125) > at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742) > at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143) > at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:210) > at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:100) > at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.handleAlreadyStartedScenario(AbstractJBossStartLaunchConfiguration.java:132) > at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.preLaunchCheck(AbstractJBossStartLaunchConfiguration.java:103) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7StartLaunchDelegate.preLaunchCheck(LocalJBoss7StartLaunchDelegate.java:39) > at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:67) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:813) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:700) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3537) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3473) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1981) MongoDB issues in Designer

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1981?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-1981: ------------------------------------ Fix Version/s: 8.5 (was: 8.4) > MongoDB issues in Designer > -------------------------- > > Key: TEIIDDES-1981 > URL: https://issues.jboss.org/browse/TEIIDDES-1981 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5 > > Attachments: MongoCP.xml, plugin.properties, plugin.xml > > > Attempt to model and query MongoDB in Designer > 1) Mongo CP is not available in default JBDS > 2) We cannot set the Mongo CP on source model - not supported. We do not have a connectionProvider -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1981) MongoDB issues in Designer

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1981?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1981: ----------------------------------------- link to related jira > MongoDB issues in Designer > -------------------------- > > Key: TEIIDDES-1981 > URL: https://issues.jboss.org/browse/TEIIDDES-1981 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.4 > > Attachments: MongoCP.xml, plugin.properties, plugin.xml > > > Attempt to model and query MongoDB in Designer > 1) Mongo CP is not available in default JBDS > 2) We cannot set the Mongo CP on source model - not supported. We do not have a connectionProvider -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1981) MongoDB issues in Designer

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1981?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1981: ----------------------------------------- Pushing to 8.5 for further consideration. Linking to another related JIRA. We've added a 'JBoss Source' CP in Designer since the last update, so the scenario is better. Preview can now be accomplished using the JBoss Source CP. 1) Create/Deploy the Mongo source using TeiidConnection importer (or create manually on server) 2) Create Source model manually 3) Create the JBoss DS CP in Designer using the JNDI name and MongoDB translator 4) Set the JBossDS CP on the source model. Continue with preview / VDB deployment as usual. > MongoDB issues in Designer > -------------------------- > > Key: TEIIDDES-1981 > URL: https://issues.jboss.org/browse/TEIIDDES-1981 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.4 > > Attachments: MongoCP.xml, plugin.properties, plugin.xml > > > Attempt to model and query MongoDB in Designer > 1) Mongo CP is not available in default JBDS > 2) We cannot set the Mongo CP on source model - not supported. We do not have a connectionProvider -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1786) Update query metadata interface for update to teiid 8.5 interface

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1786?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1786: ---------------------------------------- Paul, Our 8.4 Teiid client codebase reflects the change in methods. Have you taken this change into account when upgrading to 8.6 Teiid bits? > Update query metadata interface for update to teiid 8.5 interface > ----------------------------------------------------------------- > > Key: TEIIDDES-1786 > URL: https://issues.jboss.org/browse/TEIIDDES-1786 > Project: Teiid Designer > Issue Type: Task > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Minor > Fix For: 8.4 > > > Per Steve Hawkins 7/17/2013: > https://issues.jboss.org/browse/TEIID-2365 for 8.5 removed the ResolverVisitor.setFindShortName method so that we don't have to rely on static/ThreadLocal logic. Instead this value can be set via the QueryMetadataInterface method findShortName. A simple usage pattern is: > QueryMetadataInterface metadata = new BasicQueryMetadataWrapper(metadata){ > public boolean useOutputName() { > return false; > }; > }; > QueryResolver.resolveCommand(command, metadata); > Or this could possibly integrated into your workspace metadata in an appropriate manner (considering thread-safe usage, etc.). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2014