February 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1594) Changing Teiid server display name does not update Default Teiid Server panel name

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1594?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1594: ----------------------------------- Issue Type: Bug (was: Feature Request) > Changing Teiid server display name does not update Default Teiid Server panel name > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-1594 > URL: https://issues.jboss.org/browse/TEIIDDES-1594 > Project: Teiid Designer > Issue Type: Bug > Components: Views > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > > * Installed new kit > * Created default server but did not enter Teiid Server display name > * Started server and default mm://localhost:9999 was displayed > * Changed teiid server name to Teiid 8.2 > * Default server name panel did not show updated name -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1545) "WSDL to Relational" importer fields for Source and View Model Definition Name enter backwards in Windows

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1545?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1545: ----------------------------------- Issue Type: Bug (was: Feature Request) > "WSDL to Relational" importer fields for Source and View Model Definition Name enter backwards in Windows > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1545 > URL: https://issues.jboss.org/browse/TEIIDDES-1545 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7 > Environment: Windows 7 64 bit > JBDS 5.0 > Teiid Designer Plugin version 7.7.2.v20121025-2138-H6-GA-SOA > Reporter: Debbie Steigner > Assignee: Dan Florian > Fix For: 8.1 > > > I have only found this issue on Windows JBDS installation. Import > "WSDL File or URL >> Source and View Model" proceed thru the wizard until you reach the "Models Definition" page, do not take the default names for Source. Try entering a name, the cursor returns to column 1 after each letter so hello becomes olleh. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1550) Errors in transformations and opening transformation editor

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1550?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1550: ----------------------------------- Issue Type: Bug (was: Feature Request) > Errors in transformations and opening transformation editor > ----------------------------------------------------------- > > Key: TEIIDDES-1550 > URL: https://issues.jboss.org/browse/TEIIDDES-1550 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Blocker > Fix For: 8.1 > > Attachments: TEIIDDES-1550.zip > > > Attaching project set with 2 projects > 1) Simple Parts view transformation results in validation error; > * Select * FROM PartsSupplier.SHIP_VIA > * ERROR: The name of a symbol may not be null. > 2) Imported Flat File to create text file procedure > * Opening Transformation Editor results in error > * ERROR: Caused by: java.lang.IllegalArgumentException: RuntimeTypeConverter.getRuntimeType:Object type cannot be determined for <A.SYMBOL>. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1568) NPEs resulting from null parent mapping nodes on XML Document creation from schema

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1568?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1568: ----------------------------------- Issue Type: Bug (was: Feature Request) > NPEs resulting from null parent mapping nodes on XML Document creation from schema > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-1568 > URL: https://issues.jboss.org/browse/TEIIDDES-1568 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: Employees.xsd > > > While trying to create simple XML document for "Employee" from the attached Employees.xsd schema, there were NPE's. > 1) Import Employees.xsd in to project > 2) Select "Employee" schema element in explorer and right click "Modeling > Create XML View Documents" (XML Document Model) > 3) When finished it should create a XML document with mapping classes > Tracked in Debug and seems the created MappingDocument class does not have it's variable "parent" set which is required to walk the mapping nodes and create children. > !ENTRY org.teiid.designer.transformation 4 0 2013-01-28 08:29:47.504 > !MESSAGE > !STACK 0 > java.lang.NullPointerException > at org.teiid82.sql.impl.xml.MappingDocumentFactory.addNamespace(MappingDocumentFactory.java:66) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createNamespaceAttribute(MappingDocumentFormatter.java:833) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:787) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processChildren(MappingDocumentFormatter.java:1118) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processNamespaces(MappingDocumentFormatter.java:1198) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createDocumentNode(MappingDocumentFormatter.java:702) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:748) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMappingString(MappingDocumentFormatter.java:821) > at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformation(TreeMappingRootSqlAspect.java:285) > at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformationInfo(TreeMappingRootSqlAspect.java:333) > at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addTransformationWords(RuntimeAdapter.java:412) > at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addIndexWord(RuntimeAdapter.java:172) > at org.teiid.designer.core.index.ModelIndexer.addIndexWord(ModelIndexer.java:311) > at org.teiid.designer.core.index.ModelIndexer.index(ModelIndexer.java:164) -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1604) Switching Default Servers fails because Preview VDBs are not rebuilt.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1604?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1604: ----------------------------------- Issue Type: Bug (was: Feature Request) > Switching Default Servers fails because Preview VDBs are not rebuilt. > --------------------------------------------------------------------- > > Key: TEIIDDES-1604 > URL: https://issues.jboss.org/browse/TEIIDDES-1604 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview, VDB & Execution > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > > * Created simple Source/View model project > * Created Both AS5.1 + Teiid 7.x and AS7.1.1 + Teiid 8.2 server instances > * Started AS7 instance, set as Default Teiid Server > * Previewed tables from both source and view models > * Stopped AS7 server > * Started AS5.1 server > * Set AS5.1 as Default Teiid Server > * Tried to preview but got console log parsing errors because it found "import-vdb" element in vdb.xml file -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1607) org.teiid.designer.relational plugin has no Provider Name and incomplete Plugin Name

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1607: -------------------------------------- Summary: org.teiid.designer.relational plugin has no Provider Name and incomplete Plugin Name Key: TEIIDDES-1607 URL: https://issues.jboss.org/browse/TEIIDDES-1607 Project: Teiid Designer Issue Type: Bug Components: Documentation, Release Work Affects Versions: 8.1 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.1 Looking at 8.1 Alpha1 Teiid Designer Feature details page, the org.teiid.designer.relational plugin... * the Provider field is empty and should say "JBoss by Red Hat" * Plug-in Name == Relational. Should be "Relational Plug-in" to be consistant -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1575) Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1575?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1575: ---------------------------------------- I dislike a lot of wizards because critical "context" info isn't passed from page to page and displayed so users can make the "next" decision based on inputs they've already entered. Think about what info from Page 1 could help with Page 2, and so forth. For instance, if you've chosen DataSource_A of type mysql5.jar on Page 1, then having that info at top of Page 2 would help user select "jdbc" translator. > Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only > ------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1575 > URL: https://issues.jboss.org/browse/TEIIDDES-1575 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export, Teiid Integration > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.1 > > Attachments: ImporterPage1.png, ImporterPage2.png, WizardPage1.bmml, WizardPage1.bmml, WizardPage1.png, WizardPage2.bmml, WizardPage2.png, WizardPage3.bmml, WizardPage3.png > > > Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. > We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. > Potential DBs include: > * Hive - TEIIDDES-1193 > * Mondrian - TEIIDDES-930 > * Intersystems Cache - TEIIDDES-904 > * Ingres - TEIIDDES-883 > * LDAP - TEIIDDES-305 -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1575) Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1575?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-1575 at 2/27/13 8:33 AM: ----------------------------------------------------------------- I like it so far Mark. I get lost on a lot of wizards because critical "context" info isn't passed from page to page and displayed so users can make the "next" decision based on inputs they've already entered. Think about what info from Page 1 could help with Page 2, and so forth. For instance, if you've chosen DataSource_A of type mysql5.jar on Page 1, then having that info at top of Page 2 would help user select "jdbc" translator. was (Author: blafond): I dislike a lot of wizards because critical "context" info isn't passed from page to page and displayed so users can make the "next" decision based on inputs they've already entered. Think about what info from Page 1 could help with Page 2, and so forth. For instance, if you've chosen DataSource_A of type mysql5.jar on Page 1, then having that info at top of Page 2 would help user select "jdbc" translator. > Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only > ------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1575 > URL: https://issues.jboss.org/browse/TEIIDDES-1575 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export, Teiid Integration > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.1 > > Attachments: ImporterPage1.png, ImporterPage2.png, WizardPage1.bmml, WizardPage1.bmml, WizardPage1.png, WizardPage2.bmml, WizardPage2.png, WizardPage3.bmml, WizardPage3.png > > > Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. > We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. > Potential DBs include: > * Hive - TEIIDDES-1193 > * Mondrian - TEIIDDES-930 > * Intersystems Cache - TEIIDDES-904 > * Ingres - TEIIDDES-883 > * LDAP - TEIIDDES-305 -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1604) Switching Default Servers fails because Preview VDBs are not rebuilt.

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1604?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-1604. --------------------------------------- Resolution: Done > Switching Default Servers fails because Preview VDBs are not rebuilt. > --------------------------------------------------------------------- > > Key: TEIIDDES-1604 > URL: https://issues.jboss.org/browse/TEIIDDES-1604 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, VDB & Execution > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > > * Created simple Source/View model project > * Created Both AS5.1 + Teiid 7.x and AS7.1.1 + Teiid 8.2 server instances > * Started AS7 instance, set as Default Teiid Server > * Previewed tables from both source and view models > * Stopped AS7 server > * Started AS5.1 server > * Set AS5.1 as Default Teiid Server > * Tried to preview but got console log parsing errors because it found "import-vdb" element in vdb.xml file -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1575) Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1575?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1575: ----------------------------------------- Added mockups per discussions yesterday and today (See attached). Currently the proposed wizard will have three pages: Page1) DataSource selection - the user selects the data source (on the running 8.x+ server) that they want to use for the import. There are other 'management' features on this page. The user can add and remove dataSources here, and can set or edit the connection properties of the data sources Page2) Translator selection - the user picks which translator is to be used for the chosen data source. At bottom of page, the user selects the 'target model' for the import Page3) Difference Report - this is the standard difference report - same at that used currently in the DDL importer. > Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only > ------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1575 > URL: https://issues.jboss.org/browse/TEIIDDES-1575 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export, Teiid Integration > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.1 > > Attachments: ImporterPage1.png, ImporterPage2.png, WizardPage1.bmml, WizardPage1.bmml, WizardPage1.png, WizardPage2.bmml, WizardPage2.png, WizardPage3.bmml, WizardPage3.png > > > Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. > We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. > Potential DBs include: > * Hive - TEIIDDES-1193 > * Mondrian - TEIIDDES-930 > * Intersystems Cache - TEIIDDES-904 > * Ingres - TEIIDDES-883 > * LDAP - TEIIDDES-305 -- 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2013