February 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2927) Connection to remote DV doesn't work

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2927?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2927: ----------------------------------- Priority: Critical (was: Blocker) > Connection to remote DV doesn't work > ------------------------------------ > > Key: TEIIDDES-2927 > URL: https://issues.jboss.org/browse/TEIIDDES-2927 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 10.1 > Reporter: Bram Gadeyne > Priority: Critical > > Hi, > I'm using teiiddesigner 10.1 and teiid server 9.0.4. > I could connect to teiid in the past from the designer 10.1 (I think it was to 9.0.2 when I originally created the connection). I always see this error in the logs: > java.lang.IllegalArgumentException: admin > at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:302) > at org.teiid.runtime.client.admin.ExecutionAdmin.<init>(ExecutionAdmin.java:124) > at org.teiid.runtime.client.admin.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:53) > at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:90) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:243) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293) > at org.teiid.designer.runtime.TeiidParentServerListener$1.tryConnecting(TeiidParentServerListener.java:259) > at org.teiid.designer.runtime.TeiidParentServerListener$1.run(TeiidParentServerListener.java:197) > at java.lang.Thread.run(Thread.java:745) > And a second one later on: > java.lang.IllegalArgumentException: admin > at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:302) > at org.teiid.runtime.client.admin.ExecutionAdmin.<init>(ExecutionAdmin.java:124) > at org.teiid.runtime.client.admin.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:53) > at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:90) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:243) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293) > at org.teiid.designer.runtime.ui.server.SetDefaultServerAction$1.run(SetDefaultServerAction.java:196) > at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772) > at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227) > at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159) > at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116) > at org.teiid.designer.runtime.ui.server.SetDefaultServerAction.run(SetDefaultServerAction.java:191) > at org.teiid.designer.runtime.ui.server.SetDefaultServerAction.execute(SetDefaultServerAction.java:285) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:330) > at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator$6.linkActivated(ModelExplorerResourceNavigator.java:711) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) > at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) > at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2589) The model extension definition "relational" found in model is a different version than the one in the registry.

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2589?page=com.atlassian.jira.plu... ] Matus Makovy reopened TEIIDDES-2589: ------------------------------------ Both Quick Fixes work, but still I cannot select multiple issues of the same time and apply the fix at once - as per Lukas comment https://issues.jboss.org/browse/TEIIDDES-2589?focusedCommentId=13093786&p... > The model extension definition "relational" found in model is a different version than the one in the registry. > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2589 > URL: https://issues.jboss.org/browse/TEIIDDES-2589 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.0, 9.0.1, 9.1, 9.0.2 > Reporter: Lukas Mro > Assignee: Barry LaFond > Fix For: 10.0, 9.2.1, 11.0.1 > > > After importing model from TD 8.1.0 to 9.X.X two types of errors occures > 3 types of errors occures: > 1. The model extension definition "rest" found in model is not registered in workspace -> this one can be autofix > 2. The model extension definition "relational" found in model is a different version than the one in the registry -> This one do not have fix > 3. java.lang.StringIndexOutOfBoundsException: String index out of range: 1 > -> this one do not have fix > I`m not sure what should i send you, AMA :) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3032) Delete and create another JDG data source needs restart server.

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-3032: -------------------------------------- Summary: Delete and create another JDG data source needs restart server. Key: TEIIDDES-3032 URL: https://issues.jboss.org/browse/TEIIDDES-3032 Project: Teiid Designer Issue Type: Bug Affects Versions: 11.0.1 Reporter: Matej Kralik Attachments: screenshot.png I have a project with JDG materialization. I set CP for JDG source model and create a data source. I did some changes in CP so a wanted to update data source on the server but on the server was already data source with the same name. So I deleted this data source from the server via Servers view, refresh teiid instance, set new CP to JDG source model and created the data source from this model again but shows me this error: (screenshot) {code:java} JBAS010473: Failed to load module for RA {code} I noticed that when I restart a server, the error is gone and I am able to create other datasource. In the server's log are not any errors so I think the bug is in the designer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2959) Overriding translator isn't set automatically to source model in the VDB

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2959?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-2959: ----------------------------------- Issue Type: Feature Request (was: Bug) > Overriding translator isn't set automatically to source model in the VDB > ------------------------------------------------------------------------ > > Key: TEIIDDES-2959 > URL: https://issues.jboss.org/browse/TEIIDDES-2959 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 10.0.2 > Reporter: Matej Kralik > Attachments: screenshot1.png, screenshot2.png, screenshot3.png, screenshot4.png > > > I changed some parameters in the edit translator override window on the source model (screenshot1).I generated VDB, the overriding translator is created (screenshot2) but source model contains still default translator (screenshot3) and I have to manually set the overriding translator. I think that teiid designer should be automatically set override translator to the source model if was changed some properties in the edit translator override window.(screenshot4) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3031) Add status table to VDB automatically

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-3031: -------------------------------------- Summary: Add status table to VDB automatically Key: TEIIDDES-3031 URL: https://issues.jboss.org/browse/TEIIDDES-3031 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Affects Versions: 11.0.1 Reporter: Matej Kralik Attachments: JdgProjectFinal.zip A user has a model with JDG materialization in the project. When a user creates new VDB and adds this model to the VDB, Teiid designer adds automatically whole others model which materialization model used apart of status table. The status table must be added manually. In my opinion, would be better when Teiid designer adds this table to VDB automatically too. I have uploaded the project. When you create the vdb and add the model with materialization (BookMatView), all models are added automatically to the VDB automatically except the Status table but JDB materialization needs it too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3030) inputMessage is garbled at TeiidWSProvider when JDV booting with Shift-jis encoding

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3030?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-3030: ----------------------------------- Assignee: Ted Jones > inputMessage is garbled at TeiidWSProvider when JDV booting with Shift-jis encoding > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-3030 > URL: https://issues.jboss.org/browse/TEIIDDES-3030 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.7 > Environment: JDV 6.2.4 > JBDS 8.1.0.GA > Teiid Designer 9.0.6 (integration stack 8.0.6) and 9.0.7 > Reporter: Hiroki Daicho > Assignee: Ted Jones > Attachments: reproducer.zip > > > When logging inputvalue by SYSADMIN.logmsg on Web service (created by teiid designer), > the log message is garbled if the JDV booting with shift-jis encoding. > 1. Generate War from VDB including webservice on Teiid Designer. > 1-1. create procedure (the procedure logs input parameter by SYSADMIN.logmsg) > 1-2. modeling -> create Web Service > 1-3. create vdb includeing the web service > 1-4. modeling -> Generate SOAP war > 2. Deploy the vdb and war to JDV. > 3. JDV boot with Shift-jis encoding. > 4. call the webservice with testclient, the log will be garbled. > I attached reproducer.zip. > - testproject (JBDS project) > - testclient (webservice client) > - newvdb.war (generated web service) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2598) Export DDL should support TeiiD as DDL "Type"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2598?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-2598. ---------------------------------- Resolution: Done This was implemented as ExportTeiidDDL wizard via TEIIDDES-2681 > Export DDL should support TeiiD as DDL "Type" > --------------------------------------------- > > Key: TEIIDDES-2598 > URL: https://issues.jboss.org/browse/TEIIDDES-2598 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Tom Johnston > > I have a number of views to create. > I have created the 1st one. > I wanted the 1st one to be my template to creating the hundreds of others. > I thought through this and here was my approach. > Export the one I created as DDL. > Generate a script based upon the DDL to create the hundreds of others as one DDL file > IMPORT the DDL (teiid) as Views. > I found that there isnt a way to export already created objects as TeiiD ddl to start the process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-999) Designer importing Teradata byteint data type as bigdecimal but it should be importing as byte data type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-999?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-999. --------------------------------- Resolution: Out of Date > Designer importing Teradata byteint data type as bigdecimal but it should be importing as byte data type > -------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-999 > URL: https://issues.jboss.org/browse/TEIIDDES-999 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Warren Gibson > > BQT booleanvalue has a source data type of byteint and Designer is importing it as a bigdecimal. It should be imported as a byte. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2307) Wrong columns are presented when defining primary key

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2307?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-2307. ---------------------------------- > Wrong columns are presented when defining primary key > ----------------------------------------------------- > > Key: TEIIDDES-2307 > URL: https://issues.jboss.org/browse/TEIIDDES-2307 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.6 > Environment: teiid designer 8.6, teiid 8.7, windows 7 > Reporter: Greg MacKinnon > > I can define a primary key for a view model entity. If I then try to define a primary key on another entity in the same view model, the columns I can choose from are those related to the entity I first defined a primary key for. I can define a unique constraint on this second entity but not a primary key. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2307) Wrong columns are presented when defining primary key

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2307?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2307. ------------------------------------ Resolution: Cannot Reproduce Bug > Wrong columns are presented when defining primary key > ----------------------------------------------------- > > Key: TEIIDDES-2307 > URL: https://issues.jboss.org/browse/TEIIDDES-2307 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.6 > Environment: teiid designer 8.6, teiid 8.7, windows 7 > Reporter: Greg MacKinnon > > I can define a primary key for a view model entity. If I then try to define a primary key on another entity in the same view model, the columns I can choose from are those related to the entity I first defined a primary key for. I can define a unique constraint on this second entity but not a primary key. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2017