[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, 5 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, 5 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, 5 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, 5 months
[JBoss JIRA] Created: (TEIIDDES-171) VDB Editor allows adding multiple Salesforce generated relational models.
by Barry LaFond (JIRA)
VDB Editor allows adding multiple Salesforce generated relational models.
-------------------------------------------------------------------------
Key: TEIIDDES-171
URL: https://jira.jboss.org/jira/browse/TEIIDDES-171
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 6.0.0
Reporter: Barry LaFond
Fix For: 6.1.0
While investigating TEIIDDES-168, I tried to add a second Salesforce model to a VDB. I had already added "sf.xmi" which auto-added the XMLSOAPConnectorExtensions.xmi model. But adding "stock.xmi", which depends on a DIFFERENT XMLSOAPConnectorExtensions.xmi file, it added "stock.xmi" thinking it already had the right XMLSOAPConnectorExtensions.xmi file.
So, there is a bug here where VDB Editor should have detected the actual dependent XMLSOAPConnectorExtensions.xmi file and NOT allowed adding stock.xmi
--
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, 5 months
[JBoss JIRA] Created: (TEIIDDES-126) Add a warning for the use of a model supports property
by Steven Hawkins (JIRA)
Add a warning for the use of a model supports property
------------------------------------------------------
Key: TEIIDDES-126
URL: https://jira.jboss.org/jira/browse/TEIIDDES-126
Project: Teiid Designer
Issue Type: Quality Risk
Components: Modeling
Affects Versions: 6.0.0
Reporter: Steven Hawkins
See TEIID-131. Model support properties that are simply overrides for connector binding properties are no longer checked by the Teiid runtime, rather TEIID-205 is used to control specific capabilities through the connector binding without requiring the creation of a custom capabilities class.
Usage of 'Set Criteria Max Size', Supports "Distinct', Supports "Join", Supports "Order By", Supports "Outer Join", and Supports "Where all" should generate a warning stating that the connector binding should be used instead.
--
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, 6 months
[JBoss JIRA] Created: (TEIIDDES-417) Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled
by Paul Nittel (JIRA)
Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled
---------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-417
URL: https://jira.jboss.org/jira/browse/TEIIDDES-417
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.3
Environment: Iced Tea, Teiid Designer 6.3
Reporter: Paul Nittel
Attachments: IMFTF.jpg
I was writing a SWTBot test to create a view model's tables when I ran into this.
Knowing SWTBot can't handle the File Chooser, I was delighted to see I could enter the text file's path and name directly into the importer dialog. It wasn't until some time later that I realized merely typing in the name does nothing; you MUST enter the name using the File Chooser. (Once that's been done, it appears you can use the drop-down to re-select that file, but you need that first time entry.)
What's really bad/confusing is manually entering the file and target location enables the Finish button. Clicking it appears to work, but no tables were added to the model.
--
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, 6 months