February 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2239) Spontaneous shutdown of designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2239?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2239. ------------------------------------ Resolution: Out of Date > Spontaneous shutdown of designer > -------------------------------- > > Key: TEIIDDES-2239 > URL: https://issues.jboss.org/browse/TEIIDDES-2239 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.5.1 > Reporter: Tom Johnston > > Designer just shutdown.. (happens various times just had the time to log this particular one) > java.lang.NullPointerException > at org.eclipse.ui.internal.statushandlers.InternalDialog.refreshDialogSize(InternalDialog.java:384) > at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.doAddStatusAdapter(WorkbenchStatusDialogManagerImpl.java:273) > at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.addStatusAdapter(WorkbenchStatusDialogManagerImpl.java:197) > at org.eclipse.ui.statushandlers.WorkbenchStatusDialogManager.addStatusAdapter(WorkbenchStatusDialogManager.java:156) > at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.showStatusAdapter(WorkbenchErrorHandler.java:101) > at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:57) > at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:106) > at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36) > at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189) > at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:231) > at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:242) > at org.eclipse.ui.application.WorkbenchAdvisor.eventLoopException(WorkbenchAdvisor.java:326) > at org.eclipse.ui.internal.Workbench$3.eventLoopException(Workbench.java:491) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.handle(PartRenderingEngine.java:1134) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1124) > 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:140) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) > 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(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2000) SaveAll toolbar button enables with empty project, wont disable

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2000?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2000. ------------------------------------ Resolution: Cannot Reproduce Bug > SaveAll toolbar button enables with empty project, wont disable > --------------------------------------------------------------- > > Key: TEIIDDES-2000 > URL: https://issues.jboss.org/browse/TEIIDDES-2000 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.3 > Reporter: Mark Drilling > > I ran into a scenario in Designer where the SaveAll button enabled - with an empty project. Clicking the button does nothing and it wont disable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1859) Importing changes the parameter data type in procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1859?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1859. ------------------------------------ Resolution: Out of Date > Importing changes the parameter data type in procedure > ------------------------------------------------------ > > Key: TEIIDDES-1859 > URL: https://issues.jboss.org/browse/TEIIDDES-1859 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration > Affects Versions: 8.2 > Environment: Windows, Eclipse JUNO > Reporter: Jane Li > > When we do importing to import the newly added procedure to source model, the parameter data type is automatically changed from BigInteger to BigDecimal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1812) Remove Result Actions are not working on SQL Results View

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1812?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1812. ------------------------------------ Resolution: Out of Date newer versions of Eclipse include this fix. > Remove Result Actions are not working on SQL Results View > --------------------------------------------------------- > > Key: TEIIDDES-1812 > URL: https://issues.jboss.org/browse/TEIIDDES-1812 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution, Views > Affects Versions: 8.2 > Reporter: Mark Drilling > > After running several preview queries, I attempted to remove some of the items from the SQL Results history list. The context and toolbar 'Remove Result' and 'Remove All' actions had no effect - results were not removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1707) Data Source Created Using Model Connection Info Does Not Work

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1707?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1707. ------------------------------------ Resolution: Out of Date > Data Source Created Using Model Connection Info Does Not Work > ------------------------------------------------------------- > > Key: TEIIDDES-1707 > URL: https://issues.jboss.org/browse/TEIIDDES-1707 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.1 > Reporter: Dan Florian > > I did a JDBC import that created a relational model. I right-clicked on the new model and Modeling > Create Data Source. On the Create Data Source dialog I entered a data source name and left every other value untouched. I had to enter a password after that dialog closed. Using the newly created data source in a Teiid Connection import fails because the URL of the data source does not have the database name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1678) Jboss as7 can not deploy VDB with Relational model (XML Format)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1678?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1678. ------------------------------------ Resolution: Out of Date > Jboss as7 can not deploy VDB with Relational model (XML Format) > ---------------------------------------------------------------- > > Key: TEIIDDES-1678 > URL: https://issues.jboss.org/browse/TEIIDDES-1678 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.1 > Environment: JBDS6.0.1.GA, teiid designer 8.1.beta, jboss as 7.1 > Reporter: Lucie Fabrikova > Attachments: YahooStocksXML.xml, YahooVDB.vdb > > > I created an empty relational source model: > - Import -> designer text file -> src or view models, option Relational Model (XML Format) > JNDI Name: none, translator: yahoo (previously installed as module to jboss as 7) > I added the model to a vdb and tried to deploy it: > Error log: > TEIID70006 {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"YahooVDB.vdb\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"YahooVDB.vdb\".INSTALL: Failed to process phase INSTALL of deployment \"YahooVDB.vdb\""}} > org.teiid.adminapi.AdminProcessingException: TEIID70006 {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"YahooVDB.vdb\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"YahooVDB.vdb\".INSTALL: Failed to process phase INSTALL of deployment \"YahooVDB.vdb\""}} > at org.teiid.adminapi.AdminFactory$AdminImpl.execute(AdminFactory.java:439) > at org.teiid.adminapi.AdminFactory$AdminImpl.deploy(AdminFactory.java:695) > at org.teiid83.runtime.ExecutionAdmin.doDeployVdb(ExecutionAdmin.java:198) > at org.teiid83.runtime.ExecutionAdmin.deployVdb(ExecutionAdmin.java:176) > at org.teiid.designer.runtime.TeiidServer.deployVdb(TeiidServer.java:528) > at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:279) > at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:248) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-910) Inappropriate cross join warnings are given for nested table functions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-910?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-910. ----------------------------------- Resolution: Out of Date > Inappropriate cross join warnings are given for nested table functions > ---------------------------------------------------------------------- > > Key: TEIIDDES-910 > URL: https://issues.jboss.org/browse/TEIIDDES-910 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Modeling > Affects Versions: 7.1 > Reporter: Steven Hawkins > Priority: Minor > > The use of a nested table function reference such as TABLE(...), or any of the XMLTABLE, TEXTTABLE, etc. functions in the from clause will get warnings about possible joins. However they typically are joined by sideways correlation, not through a join/where condition. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1245) Copy/paste XmML doc into same model does not correct attributes in choice criteria

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1245?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1245. ------------------------------------ Resolution: Won't Fix > Copy/paste XmML doc into same model does not correct attributes in choice criteria > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-1245 > URL: https://issues.jboss.org/browse/TEIIDDES-1245 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.4 > Environment: JBDS 4.1.2 > Reporter: Paul Nittel > > In the BookSetMixed end-to-end test script, the completed document (bookSetMixedDocument) is copied, pasted, and renamed to bookSetMixedDocument1. This works well, except in the case of the choice criteria where the name remains bookSetMixedDocument. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-829) Duplicate "Schema" name generated while creating XML transformations from XSD

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-829?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-829. ----------------------------------- Resolution: Won't Fix > Duplicate "Schema" name generated while creating XML transformations from XSD > ----------------------------------------------------------------------------- > > Key: TEIIDDES-829 > URL: https://issues.jboss.org/browse/TEIIDDES-829 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Environment: F14 JBDS-CR2 > Reporter: Ramesh Reddy > > 1) Imported the Books.xsd, BookDataTypes.xsd > 2) Open the Books, xml schema and select "bibilography" element > 3) Right click "Modeling -> Create XML to Scalar Transformation" > 4) That generates a procedure in a view model with schema name "bibiligraphy" > 5) Right click "Modeling -> Create Scalar to XMl transformation" > 6) That generates a another procedure in a view model with duplicate schema name "bibiligraphy" > it should not even generate "schema" folder, just generate the procedure in the selected view model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-306) xsi:type attributes not being created in XML document instances when required

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-306?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-306. ----------------------------------- Resolution: Won't Fix > xsi:type attributes not being created in XML document instances when required > ----------------------------------------------------------------------------- > > Key: TEIIDDES-306 > URL: https://issues.jboss.org/browse/TEIIDDES-306 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Reporter: John Verhaeg > Priority: Minor > > When an XSD element or its type is marked as abstract, the concrete elements used in the instance document to represent the abstract element must contain an xsi:type attribute with a concrete type as a value. It seems the best way to handle this in the future would be to add a new "type criteria" property and editor to transformations that would behave somewhat like the choice criteria editor. The editor would prompt the user specify one or more concrete types along with criteria used by the server to determine which type to use for a given set of data. This defect is a carryover from defect 20067 in Defect Tracker. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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