[JBoss JIRA] Created: (TEIIDDES-191) XSD as Relational importer has problems with child elements with many parents
by Greg Haber (JIRA)
XSD as Relational importer has problems with child elements with many parents
-----------------------------------------------------------------------------
Key: TEIIDDES-191
URL: https://jira.jboss.org/jira/browse/TEIIDDES-191
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.0.0
Environment: Teiid Designer 6.0.0 official (14 May 2009) release
Reporter: Greg Haber
Attachments: address.xsd, person.xsd, person2.xml, person2.xsd
I've encountered a lot of problems with the Teiid Designer XML as Relational Importer (and with its legacy ancestor) dealing with importing XSDs where a child element has multiple parents. The importer currently treats all elements throughout the XSD that have the same name and type as the same, and so models that element(s) as a single table with multiple parents, if the number of parents is above a configurable number (currently defaults to 3).
Which is all well and good in theory, but in practice it seems to hit a number of problems
1) During the import process, if the selection of document root elements is left at the default, not all needed tables are generated. See person.xsd example attached.
2) If all possible root elements are selected, it looks mostly right, but there are often extra elements in the child tables (again try with person.xsd). Plus, the tables don't actually work at runtime correctly (try using attached person2.xml as the data source - notice that you can only get to the spouse's father from Person, not to their own father).
I've also attached some other example problem XSDs - person2.xsd, and address.xsd
Now, in some cases a reasonable workaround is to up the number of allowed parents parameter, so that everything gets folded into a single table. But that isn't a general solution, as it doesn't work with things like person2.xsd.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Created: (TEIIDDES-228) Import transformation SQL fails to do anything
by Paul Nittel (JIRA)
Import transformation SQL fails to do anything
----------------------------------------------
Key: TEIIDDES-228
URL: https://jira.jboss.org/jira/browse/TEIIDDES-228
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.2.0
Environment: Fedora 10, Designer 20090922 build (same thing with RC1)
Reporter: Paul Nittel
I exported the transformation SQL from the VQT model. When I tried to import the SQL into a new VQT model, it gave the appearance it completed successfully, but none of the tables were defined. There were no errors or exceptions found in the log.
The format of the exported file is not the same as that of the Metadata Text Importer, so to use that route the file must be edited. (The export version takes into account the SELECT, INSERT, UPDATE, DELETE possibilities.) BTW, this had issues as well, but that's another JIRA.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIIDDES-181) Missing Java SQL Types In RelationalTypeMapping Interface And Implementation Class
by Dan Florian (JIRA)
Missing Java SQL Types In RelationalTypeMapping Interface And Implementation Class
----------------------------------------------------------------------------------
Key: TEIIDDES-181
URL: https://jira.jboss.org/jira/browse/TEIIDDES-181
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.0.0
Reporter: Dan Florian
The following java.sql.Types constants do not have constants in RelationalTypeMapping or mappings in RelationalTypeMappingImpl: DATALINK, BOOLEAN, ROWID, LONGNVARCHAR, NCLOB, and SQLXML. All but the first 2 were added in JDK 1.6. Need to provide the mapping to the metamatrix datatypes for each or determine a mapping is not needed.
Also may want to look at using or referencing com.metamatrix.common.types.MMJDBCSQLTypeInfo instead of maintaining the mapping in two differenct classes.
See TEIIDDES-179 where NVARCHAR was added to fix this defect.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIIDDES-229) Textual Metadata Importer fails to create simple virtual table transformations
by Paul Nittel (JIRA)
Textual Metadata Importer fails to create simple virtual table transformations
------------------------------------------------------------------------------
Key: TEIIDDES-229
URL: https://jira.jboss.org/jira/browse/TEIIDDES-229
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.2.0
Environment: Fedora 10, Designer build 20090922
Reporter: Paul Nittel
Importing the attached file into the VQT model of the attached model project set concludes wit mixed results. Some of the transformations are success while others fail. Even the simplest fail. The results appear to be very consistent as I've tried this a few time with the same outcome.
1 - Start Designer
2 - Import model project set
3 - Select VQT model
4 - Right-click VQT > Import > Metadata from Text
5 - Follow the Wizard
6 - Navigate to, and choose, the VqtTransformationSqlForTextImport.txt file
7 - Select the VQT model
8 - Finish
In my case, the MAPPING tables (1 - 4) each have null transformations. Copying and pasting in the transformations specified in the file all work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIIDDES-260) Problems in New Model Wizard after backing up to Select different Metamodel type
by Barry LaFond (JIRA)
Problems in New Model Wizard after backing up to Select different Metamodel type
--------------------------------------------------------------------------------
Key: TEIIDDES-260
URL: https://jira.jboss.org/jira/browse/TEIIDDES-260
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 7.0
Reporter: Barry LaFond
Fix For: 7.0
Open Designer and make sure you have a Relational and Web service model in workspace (i.e. import relational and create WS via "Modeling >> Create Web Service" action.
1) Select "New Metadata Model"
2) Select "Relational" metamodel and "Source" model type (click NEXT)
3) Select Relational model in workspace (via "..." browse button) (notice selecting non-relational models results in error message in model selection dialog) (click OK)
4) Select "Back" button to return to selecting model types
5) Select "Web Service" metamodel (click NEXT)
6) Select Web Service model in workspace (via "..." browse button).
7) Note that error message says that user must select a "Relational" model.
This is wrong and basically the MetaModelDescriptor isn't getting updated on the StructuralCopyWizard & TreeViewerWizardPanel.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months