October 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1885) DDL importer problems for both source and view models

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1885: ---------------------------------------- I wasn't able to repeat the scenario as above... what I found was 1) Import attached DDL file 2) The DDL Importer comes up defaulted to TEIID dialect and Auto-Select == FALSE * This results in a parsing error on Differences page since the DDL file does not contain Teiid Dialect and the importer was forced to try and parse the DDL using Modeshape DDL Parser 3) Turning Auto-select == TRUE and clicking NEXT * This results in no error on the Differences page since the importer should have discovered/used the standard SQL92 dialect. 4) FINISH created the desired models > DDL importer problems for both source and view models > ------------------------------------------------------ > > Key: TEIIDDES-1885 > URL: https://issues.jboss.org/browse/TEIIDDES-1885 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.3 > > Attachments: stdcust.ddl > > > When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear: > a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message. > b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error. > The DDL in question works in JBDS 6 and earlier. > Version-Release number of selected component (if applicable): > JBDS 7 with JBDSIS 7 beta 4 > How reproducible: > Consistent. > Steps to Reproduce: > Import attached DDL via importer. > see: https://bugzilla.redhat.com/show_bug.cgi?id=1016553 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1632) validation problems with trim and concat used together - 7.7.x

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1632?page=com.atlassian.jira.plu... ] Debbie Steigner commented on TEIIDDES-1632: ------------------------------------------- I see validations errors when using TRIM without concat. Using the latest 7.7.4.v20130801-1634-H7-Final , Create a new view base table and make it's transformation: select trim ( leading '+' from '++++Test') trim_col1 Save and the validator changes it to: SELECT Trim(leading FROM ) AS trim_col1 Which gives you parsing errors. Weird if you then open the expression builder it shows the correct items. > validation problems with trim and concat used together - 7.7.x > -------------------------------------------------------------- > > Key: TEIIDDES-1632 > URL: https://issues.jboss.org/browse/TEIIDDES-1632 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 7.7 > Reporter: Johnathon Lee > Assignee: Johnathon Lee > Fix For: 7.7.3 > > Attachments: Trimtest.zip > > > Using the latest JBDS 5.0 and the attached simplified Model Project Set (Trimtest.zip). > On the view model CCH_V.memmasV change the transformation to [1] and perform a Save/Validate. It will be rewritten to [2] and give a parsing error. > [1] > SELECT > ltrim(Memb.LSTNAM) || ', ' || trim('foo') ||' '|| trim(Memb.MIDNAM) AS MEMBER_NAME > FROM > CCH.MEMMAS AS Memb > [2] > SELECT > ((((ltrim(Memb.LSTNAM) || ', ') || trim( FROM )) || ' ') || trim( FROM Memb.MIDNAM)) AS MEMBER_NAME > FROM > CCH.MEMMAS AS Memb -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1886) Automatically modify a column name at creating view model from XML schema

by hisao furuichi (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1886?page=com.atlassian.jira.plu... ] hisao furuichi commented on TEIIDDES-1886: ------------------------------------------ Hi. This is the reproduction step. 1. Create two xsd file. test1.xsd ==== <?xml version="1.0" encoding="UTF-8" standalone="no"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.example.org/dictionary_b" elementFormDefault="qualified" targetNamespace="http://www.example.org/dictionary_b"> <element name="column_a" type="string" /> <element name="column_b" type="string" /> <complexType name="table_a"> <sequence> <element ref="tns:column_a" /> <element ref="tns:column_b" /> </sequence> </complexType> <complexType name="table_b"> <sequence> <element ref="tns:column_a" /> <element ref="tns:column_b" /> </sequence> </complexType> </schema> ==== test2.xsd ==== <?xml version="1.0" encoding="UTF-8" standalone="no"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.example.org/dictionay_a" elementFormDefault="qualified" targetNamespace="http://www.example.org/dictionay_a"> <element name="column_a" type="string"/> <element name="column_b" type="string"/> <element name="table_a"> <complexType> <sequence> <element ref="tns:column_a"/> <element ref="tns:column_b"/> </sequence> </complexType> </element> <element name="table_b"> <complexType> <sequence> <element ref="tns:column_a"/> <element ref="tns:column_b"/> </sequence> </complexType> </element> </schema> ==== 2. Import schema files using teiid designer. Teiid designer project -> Right click -> import -> Teiid designer -> XML Schemas 3. Create view model from schemas XSD -> Right click -> Modeling -> Create Relational View Model from Schema action Thx > Automatically modify a column name at creating view model from XML schema > ------------------------------------------------------------------------- > > Key: TEIIDDES-1886 > URL: https://issues.jboss.org/browse/TEIIDDES-1886 > Project: Teiid Designer > Issue Type: Bug > Components: Views > Affects Versions: 7.7.2 > Environment: Fedora 18 > JBoss Developer Studio 5 > Reporter: hisao furuichi > > Teiid designer modify column names automatically even if it's not necessary. I'll write 2 examples to describe this issue. > 1. In the case of the view model from following schema, even if there are the same column names on the different table, it is numbered automatically. > (I think that the nameValidator object should be created as new instance every table or table's columns in GenerateVirtualFromXsdHelper.java.) > <complexType name="table_a"> > <sequence> > <element ref="tns:column_a" /> > <element ref="tns:column_b" /> > </sequence> > </complexType> > <complexType name="table_b"> > <sequence> > <element ref="tns:column_a" /> > <element ref="tns:column_b" /> > </sequence> > </complexType> > 2. If there is a parent element to a column like the following schema, the parent element name is added before column names. > (See GenerateVirtualFromXsdHelper.java line 213 [2].) > <element name="table_a"> > <complexType> > <sequence> > <element ref="tns:column_a"/> > <element ref="tns:column_b"/> > </sequence> > </complexType> > </element> > <element name="table_b"> > <complexType> > <sequence> > <element ref="tns:column_a"/> > <element ref="tns:column_b"/> > </sequence> > </complexType> > </element> -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1886) Automatically modify a column name at creating view model from XML schema

by hisao furuichi (JIRA)

hisao furuichi created TEIIDDES-1886: ---------------------------------------- Summary: Automatically modify a column name at creating view model from XML schema Key: TEIIDDES-1886 URL: https://issues.jboss.org/browse/TEIIDDES-1886 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 7.7.2 Environment: Fedora 18 JBoss Developer Studio 5 Reporter: hisao furuichi Teiid designer modify column names automatically even if it's not necessary. I'll write 2 examples to describe this issue. 1. In the case of the view model from following schema, even if there are the same column names on the different table, it is numbered automatically. (I think that the nameValidator object should be created as new instance every table or table's columns in GenerateVirtualFromXsdHelper.java.) <complexType name="table_a"> <sequence> <element ref="tns:column_a" /> <element ref="tns:column_b" /> </sequence> </complexType> <complexType name="table_b"> <sequence> <element ref="tns:column_a" /> <element ref="tns:column_b" /> </sequence> </complexType> 2. If there is a parent element to a column like the following schema, the parent element name is added before column names. (See GenerateVirtualFromXsdHelper.java line 213 [2].) <element name="table_a"> <complexType> <sequence> <element ref="tns:column_a"/> <element ref="tns:column_b"/> </sequence> </complexType> </element> <element name="table_b"> <complexType> <sequence> <element ref="tns:column_a"/> <element ref="tns:column_b"/> </sequence> </complexType> </element> -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1871) NPE While using DDL based importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1871?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1871: ----------------------------------- Priority: Blocker (was: Major) > NPE While using DDL based importer > ---------------------------------- > > Key: TEIIDDES-1871 > URL: https://issues.jboss.org/browse/TEIIDDES-1871 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ramesh Reddy > Priority: Blocker > Attachments: sap-flight.ddl, working_sap_flight.ddl > > > While importing the OData translator based DDL, encountered the below NPE. > {code} > Caused by: java.lang.NullPointerException > at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.getColumnNode(CreateTableParser.java:117) > at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseReferenceList(CreateTableParser.java:330) > at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBodyConstraint(CreateTableParser.java:453) > at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBody(CreateTableParser.java:362) > at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parse(CreateTableParser.java:195) > at org.modeshape.sequencer.ddl.dialect.teiid.TeiidDdlParser.parseNextStatement(TeiidDdlParser.java:150) > at org.modeshape.sequencer.ddl.StandardDdlParser.parse(StandardDdlParser.java:209) > at org.modeshape.sequencer.ddl.DdlParsers.parseUsing(DdlParsers.java:152) > at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:134) > at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:106) > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:40) > at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:90) > at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:222) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1495) New Source Function action disabled if one already exists in model

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1495?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1495: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 996292|https://bugzilla.redhat.com/show_bug.cgi?id=996292] from MODIFIED to ON_QA > New Source Function action disabled if one already exists in model > ------------------------------------------------------------------ > > Key: TEIIDDES-1495 > URL: https://issues.jboss.org/browse/TEIIDDES-1495 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.7, 7.8 > Reporter: Barry LaFond > Assignee: Dan Florian > Priority: Critical > Fix For: 8.0 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1100) Using Flat File Importer, it doesn't recognize "\n" or "\r\n" in the file

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1100?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1100: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 780971|https://bugzilla.redhat.com/show_bug.cgi?id=780971] from MODIFIED to ON_QA > Using Flat File Importer, it doesn't recognize "\n" or "\r\n" in the file > ------------------------------------------------------------------------- > > Key: TEIIDDES-1100 > URL: https://issues.jboss.org/browse/TEIIDDES-1100 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Environment: Windows > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: test.csv > > > Trying to use the Import from Flat File option, but it doesn't recognize linefeeds of "\n" or "\r\n". > This also occurs for the DDL importer. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1777) Unable to connect to a remote domain server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1777?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1777: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 982648|https://bugzilla.redhat.com/show_bug.cgi?id=982648] from MODIFIED to ON_QA > Unable to connect to a remote domain server > ------------------------------------------- > > Key: TEIIDDES-1777 > URL: https://issues.jboss.org/browse/TEIIDDES-1777 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.2 > Reporter: Van Halbert > Priority: Critical > > Unable to connect to a remote domain server. Getting the following exception: > !ENTRY org.teiid.designer.dqp 4 0 2013-07-08 16:58:31.613 > !MESSAGE TEIID70036 java.lang.IllegalArgumentException > !STACK 0 > org.teiid.adminapi.AdminProcessingException: TEIID70036 java.lang.IllegalArgumentException > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1433) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1) > at org.teiid83.runtime.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:659) > at org.teiid83.runtime.ExecutionAdmin.init(ExecutionAdmin.java:576) > at org.teiid83.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:137) > at org.teiid83.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:29) > at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:212) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:232) > at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:58) > 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:3976) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) > 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.RefreshServerAction.run(RefreshServerAction.java:54) > at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) > 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$5.handleEvent(ActionContributionItem.java:411) > 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: java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194) > at org.teiid.adminapi.AdminFactory$AdminImpl.getDomainAwareList(AdminFactory.java:1349) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1430) > ... 51 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1778) Change the Teiid Server version in the preferences to 8.4

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1778?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1778: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 982648|https://bugzilla.redhat.com/show_bug.cgi?id=982648] from MODIFIED to ON_QA > Change the Teiid Server version in the preferences to 8.4 > --------------------------------------------------------- > > Key: TEIIDDES-1778 > URL: https://issues.jboss.org/browse/TEIIDDES-1778 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Paul Richardson > Attachments: teiid-default-server-version.png > > > The Teiid Designer preference for Teiid Server version is defaulting to 8.3, this should be 8.4 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1364) Validating WSDL imported from Amazon.com fails with NPE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1364?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1364: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 825293|https://bugzilla.redhat.com/show_bug.cgi?id=825293] from MODIFIED to ON_QA > Validating WSDL imported from Amazon.com fails with NPE > ------------------------------------------------------- > > Key: TEIIDDES-1364 > URL: https://issues.jboss.org/browse/TEIIDDES-1364 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Environment: JBDS 5.0 Beta 3 with SOAtooling > Reporter: Paul Nittel > Assignee: Ted Jones > Fix For: 8.1 > > Attachments: AmazonWsdlFailed_NPE.png > > > When I imported WSDL from http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl I received a null pointer exception on the validation page of the WSDL to Web service model wizard. There was no entry in the Designer's log file. A screenshot of the error is attached. -- 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, 6 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 October 2013