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 Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1918: ----------------------------------------- I see where the type mismatch is ocurring. Will discuss potential fix with Barry tomorrow. Also need to go thru a couple 'VDB source model' scenarios with him. > 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-1927) Need to test scenarios where vdb source translators are changed.

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1927: --------------------------------------- Summary: Need to test scenarios where vdb source translators are changed. Key: TEIIDDES-1927 URL: https://issues.jboss.org/browse/TEIIDDES-1927 Project: Teiid Designer Issue Type: Task Components: VDB & Execution Affects Versions: 8.2 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.3 I encountered a couple confusing scenarios where I changed the translator on a vdb source, but had no change on execution in designer. We need to test to ensure that vdb is picking up translator changes as expected. Scenario - Import a source Model (in my case it was SF). - Create a VDB and add the source model to it. - Deploy VDB, execute query to verify can query ok. - Change source translator in VDB to 'loopback'. Save VDB - Redeploy VDB, then run query. Loopback was expected, but I still got SF data back 1) the scenario above changes the translator in the VDB, but there is still an annotation in the source model with 'translator=salesforce'. So they are in conflict. 2) Changed the source model annotation translator to 'loopback', resync'd the vdb, redeployed and queried again. Still got SF results instead of loopback. The re-deployment is not picking up the translator change. 3) Finally, in the server view, manually 'un-deployed' the vdb. then went back to model exployer and deployed again. Then I got loopback results. -- 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-1885) DDL importer problems - TeiidServerManager initialization problem

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-1885: ------------------------------------ Summary: DDL importer problems - TeiidServerManager initialization problem (was: DDL importer problems for both source and view models) > DDL importer problems - TeiidServerManager initialization problem > ------------------------------------------------------------------ > > 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: Mark Drilling > Fix For: 8.3 > > Attachments: ddl-import, 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, 5 months

1
0
0 / 0

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

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1885: ----------------------------------------- >From the log, the root cause: Root exception: java.lang.RuntimeException: java.lang.RuntimeException: Programming error: The TeiidServerManager is being used before it has been initialised at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2199) at org.teiid.designer.metamodels.relational.util.RelationalTypeMappingImpl.getDatatype(RelationalTypeMappingImpl.java:156) at org.teiid.designer.metamodels.relational.util.RelationalTypeMappingImpl.getDatatype(RelationalTypeMappingImpl.java:133) at org.teiid.designer.ddl.importer.node.StandardImporter.getTeiidDataTypeName(StandardImporter.java:291) at org.teiid.designer.ddl.importer.node.StandardImporter.createColumn(StandardImporter.java:315) at org.teiid.designer.ddl.importer.node.StandardImporter.createObject(StandardImporter.java:602) at org.teiid.designer.ddl.importer.node.StandardImporter.importNode(StandardImporter.java:571) at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:180) 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) Caused by: java.lang.RuntimeException: Programming error: The TeiidServerManager is being used before it has been initialised at org.teiid.designer.runtime.TeiidServerManager.checkStarted(TeiidServerManager.java:325) at org.teiid.designer.runtime.TeiidServerManager.getDefaultServerVersion(TeiidServerManager.java:418) at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2197) ... 12 more > 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: Mark Drilling > Fix For: 8.3 > > Attachments: ddl-import, 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, 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 commented on TEIIDDES-1926: ---------------------------------------- Can you check the log for this test also? and attach if it contains errors? > 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-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 reopened TEIIDDES-1885: ------------------------------------ Assignee: Mark Drilling (was: Barry LaFond) > 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: Mark Drilling > Fix For: 8.3 > > Attachments: ddl-import, 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, 5 months

1
0
0 / 0

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

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ] Lucie Fabrikova updated TEIIDDES-1885: -------------------------------------- Attachment: ddl-import > 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: ddl-import, 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1925) Cannot import from Flat File Source on MacOS

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1925?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1925. ------------------------------------ Resolution: Done replaced stripping ".txt" from the file name to using IPath methods to remove extension. Fixes CSV file issue > Cannot import from Flat File Source on MacOS > -------------------------------------------- > > Key: TEIIDDES-1925 > URL: https://issues.jboss.org/browse/TEIIDDES-1925 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Environment: MacOS X 10.8, java oracle 1.7 and apple 1.6, JBDS 7 > Reporter: Lucie Fabrikova > Assignee: Barry LaFond > Fix For: 8.3 > > Attachments: items.csv, macos-flatfile-import.png > > > Flat file source import wizard behaves erroneously on page "View Model Definition": after setting data file source, data files, location and name ("ItemSource", by default was "item_source"), the "Next" button produces an error message: "View table name invalid. ..." -- 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-1925) Cannot import from Flat File Source on MacOS

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1925?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1925: ---------------------------------------- I think the real issue here is that the view table name is generated with the full "items.csv" file name. If I use "items.txt", then the ".txt" is stripped off. Need to add that logic. > Cannot import from Flat File Source on MacOS > -------------------------------------------- > > Key: TEIIDDES-1925 > URL: https://issues.jboss.org/browse/TEIIDDES-1925 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Environment: MacOS X 10.8, java oracle 1.7 and apple 1.6, JBDS 7 > Reporter: Lucie Fabrikova > Assignee: Barry LaFond > Fix For: 8.3 > > Attachments: items.csv, macos-flatfile-import.png > > > Flat file source import wizard behaves erroneously on page "View Model Definition": after setting data file source, data files, location and name ("ItemSource", by default was "item_source"), the "Next" button produces an error message: "View table name invalid. ..." -- 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-1925) Cannot import from Flat File Source on MacOS

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1925?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1925: ----------------------------------- Fix Version/s: 8.3 Assignee: Barry LaFond Component/s: Import/Export > Cannot import from Flat File Source on MacOS > -------------------------------------------- > > Key: TEIIDDES-1925 > URL: https://issues.jboss.org/browse/TEIIDDES-1925 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Environment: MacOS X 10.8, java oracle 1.7 and apple 1.6, JBDS 7 > Reporter: Lucie Fabrikova > Assignee: Barry LaFond > Fix For: 8.3 > > Attachments: items.csv, macos-flatfile-import.png > > > Flat file source import wizard behaves erroneously on page "View Model Definition": after setting data file source, data files, location and name ("ItemSource", by default was "item_source"), the "Next" button produces an error message: "View table name invalid. ..." -- 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