November 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1918) JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1918: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1026892|https://bugzilla.redhat.com/show_bug.cgi?id=1026892] from ASSIGNED to MODIFIED > JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1918 > URL: https://issues.jboss.org/browse/TEIIDDES-1918 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.3 > > > When a VDB is imported(reused) by another VDB and the imported VDB contains table with column of type integer, then the importing VDB will throw validation error. > Steps to reproduce: > 1. Create loopback VDB, add table DATA with two columns, one of type integer and one of the string > 2. Deploy the loopback VDB > 3. Reuse the looback VDB > 3.1. Import the loopback VDB through JDBC importer > "Import as VDB source model" have to be checked > 3.2 Create view model, use table DATA in the view model > 3.3 Create and deploy new VDB > When deploying the VDB, error occures: > TEIID31080 View data validation error: QueryValidatorException-The definition for data has the wrong type for column 1. Expected bigdecimal, but was biginteger. > 15:57:48,718 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40073 The metadata for the VDB aaa.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. > 15:57:48,719 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40003 VDB aaa.1 is set to FAILED -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1918) JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1918: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1026892|https://bugzilla.redhat.com/show_bug.cgi?id=1026892] from ASSIGNED to MODIFIED > JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1918 > URL: https://issues.jboss.org/browse/TEIIDDES-1918 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.3 > > > When a VDB is imported(reused) by another VDB and the imported VDB contains table with column of type integer, then the importing VDB will throw validation error. > Steps to reproduce: > 1. Create loopback VDB, add table DATA with two columns, one of type integer and one of the string > 2. Deploy the loopback VDB > 3. Reuse the looback VDB > 3.1. Import the loopback VDB through JDBC importer > "Import as VDB source model" have to be checked > 3.2 Create view model, use table DATA in the view model > 3.3 Create and deploy new VDB > When deploying the VDB, error occures: > TEIID31080 View data validation error: QueryValidatorException-The definition for data has the wrong type for column 1. Expected bigdecimal, but was biginteger. > 15:57:48,718 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40073 The metadata for the VDB aaa.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. > 15:57:48,719 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40003 VDB aaa.1 is set to FAILED -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1926) Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1926?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1926: ----------------------------------- Assignee: Ted Jones > Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1926 > URL: https://issues.jboss.org/browse/TEIIDDES-1926 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3 > Environment: java 1.6 apple, JBDS 7, MacOS 10.8 > Reporter: Lucie Fabrikova > Assignee: Ted Jones > Fix For: 8.3 > > Attachments: macos-xml-import-jdk1.6.png > > > Importing from XML file source on MacOS via importer wizard shows following pages: > "XML Data File Source Selection" - after setting all data and clicking on Next, page "View Model Definition" is showed - viz attachment. The Next button is disabled. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1918) JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1918. ------------------------------------- Resolution: Done Resolved type mismatch issue pull request - https://github.com/Teiid-Designer/teiid-designer/pull/259 > JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1918 > URL: https://issues.jboss.org/browse/TEIIDDES-1918 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.3 > > > When a VDB is imported(reused) by another VDB and the imported VDB contains table with column of type integer, then the importing VDB will throw validation error. > Steps to reproduce: > 1. Create loopback VDB, add table DATA with two columns, one of type integer and one of the string > 2. Deploy the loopback VDB > 3. Reuse the looback VDB > 3.1. Import the loopback VDB through JDBC importer > "Import as VDB source model" have to be checked > 3.2 Create view model, use table DATA in the view model > 3.3 Create and deploy new VDB > When deploying the VDB, error occures: > TEIID31080 View data validation error: QueryValidatorException-The definition for data has the wrong type for column 1. Expected bigdecimal, but was biginteger. > 15:57:48,718 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40073 The metadata for the VDB aaa.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. > 15:57:48,719 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40003 VDB aaa.1 is set to FAILED -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1924) Unable to edit the translator overridden property

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1924?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1924. ------------------------------------- Resolution: Done Resolved - pull request https://github.com/Teiid-Designer/teiid-designer/pull/260 > Unable to edit the translator overridden property > ------------------------------------------------- > > Key: TEIIDDES-1924 > URL: https://issues.jboss.org/browse/TEIIDDES-1924 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.3 > > > Trying to edit the property (fix the name) in the translator override. However, when I clicked the 'edit' button, nothing happened. Couldn't edit the property name or couldn't decern that anything was editable. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1924) Unable to edit the translator overridden property

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1924?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-1924: ------------------------------------ Fix Version/s: 8.3 > Unable to edit the translator overridden property > ------------------------------------------------- > > Key: TEIIDDES-1924 > URL: https://issues.jboss.org/browse/TEIIDDES-1924 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.3 > > > Trying to edit the property (fix the name) in the translator override. However, when I clicked the 'edit' button, nothing happened. Couldn't edit the property name or couldn't decern that anything was editable. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1924) Unable to edit the translator overridden property

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1924?page=com.atlassian.jira.plu... ] Mark Drilling reassigned TEIIDDES-1924: --------------------------------------- Assignee: Mark Drilling > Unable to edit the translator overridden property > ------------------------------------------------- > > Key: TEIIDDES-1924 > URL: https://issues.jboss.org/browse/TEIIDDES-1924 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > > Trying to edit the property (fix the name) in the translator override. However, when I clicked the 'edit' button, nothing happened. Couldn't edit the property name or couldn't decern that anything was editable. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1926) Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1926?page=com.atlassian.jira.plu... ] Lucie Fabrikova updated TEIIDDES-1926: -------------------------------------- Attachment: macos-xml-import-jdk1.6.png > Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1926 > URL: https://issues.jboss.org/browse/TEIIDDES-1926 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3 > Environment: java 1.6 apple, JBDS 7, MacOS 10.8 > Reporter: Lucie Fabrikova > Fix For: 8.3 > > Attachments: macos-xml-import-jdk1.6.png > > > Importing from XML file source on MacOS via importer wizard shows following pages: > "XML Data File Source Selection" - after setting all data and clicking on Next, page "View Model Definition" is showed - viz attachment. The Next button is disabled. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1926) Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1926?page=com.atlassian.jira.plu... ] Lucie Fabrikova commented on TEIIDDES-1926: ------------------------------------------- Unless I am mistaken, the log was empty. > Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1926 > URL: https://issues.jboss.org/browse/TEIIDDES-1926 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3 > Environment: java 1.6 apple, JBDS 7, MacOS 10.8 > Reporter: Lucie Fabrikova > Fix For: 8.3 > > > Importing from XML file source on MacOS via importer wizard shows following pages: > "XML Data File Source Selection" - after setting all data and clicking on Next, page "View Model Definition" is showed - viz attachment. The Next button is disabled. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1779) Designer error when trying to read a remote server configuration that's running in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1779?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1779: --------------------------------------------------- belong(a)redhat.com made a comment on [bug 982741|https://bugzilla.redhat.com/show_bug.cgi?id=982741] Van, Please review the Doc Text for this and add a workaround if one exists. Cheers, Ben > Designer error when trying to read a remote server configuration that's running in domain mode > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1779 > URL: https://issues.jboss.org/browse/TEIIDDES-1779 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Paul Richardson > Priority: Blocker > Fix For: 8.4 > > > org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [{"subsystem" => "teiid"}]. Failure was "JBAS014883: No resource definition is registered for address [(\"subsystem\" => \"teiid\")]". > at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336) > 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:58) > at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.getTeiidRuntimeVersion(JBoss7ServerUtil.java:172) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.createJboss7TeiidServer(TeiidServerAdapterFactory.java:204) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:185) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:78) > at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:66) > at org.eclipse.wst.server.core.internal.ResourceManager.fireServerEvent(ResourceManager.java:560) > at org.eclipse.wst.server.core.internal.ResourceManager.addServer(ResourceManager.java:712) > at org.eclipse.wst.server.core.internal.Server.saveToMetadata(Server.java:474) > at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:266) > at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:463) > at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:432) > at org.eclipse.wst.server.ui.internal.editor.ServerEditor.doSave(ServerEditor.java:389) > at org.eclipse.ui.internal.DefaultSaveable.doSave(DefaultSaveable.java:54) > at org.eclipse.ui.Saveable.doSave(Saveable.java:214) > at org.eclipse.ui.internal.SaveableHelper.doSaveModel(SaveableHelper.java:348) > at org.eclipse.ui.internal.WorkbenchPage$11.run(WorkbenchPage.java:3633) > at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:276) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) > at org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:1812) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1809) > at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:284) > at org.eclipse.ui.internal.WorkbenchPage.saveAll(WorkbenchPage.java:3644) > at org.eclipse.ui.internal.WorkbenchPage.saveAllEditors(WorkbenchPage.java:3440) > at org.eclipse.ui.internal.handlers.SaveAllHandler.execute(SaveAllHandler.java:47) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [{"subsystem" => "teiid"}]. Failure was "JBAS014883: No resource definition is registered for address [(\"subsystem\" => \"teiid\")]". > at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:327) > ... 76 more -- 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

12 years, 5 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 November 2013