June 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-995) Importing metadata from text, VARCHAR is interpreted as OBJECT - Should be character-based type

by Paul Nittel (JIRA)

Importing metadata from text, VARCHAR is interpreted as OBJECT - Should be character-based type ----------------------------------------------------------------------------------------------- Key: TEIIDDES-995 URL: https://issues.jboss.org/browse/TEIIDDES-995 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.4 Environment: Designer 7.4 in Eclipse 3.6 Reporter: Paul Nittel I imported the attached CSV file into a relational source model. The NUMBERs translated to bigdecimal, but the VARCHARs translated to objects. Should have been a character-based type. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
6
0 / 0

[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

14 years, 9 months

2
5
0 / 0

[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

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-189) Plugin details shows version, but not build number

by Paul Nittel (JIRA)

Plugin details shows version, but not build number -------------------------------------------------- Key: TEIIDDES-189 URL: https://jira.jboss.org/jira/browse/TEIIDDES-189 Project: Teiid Designer Issue Type: Bug Components: Build Affects Versions: 6.0.0 Environment: Fedora 10 Reporter: Paul Nittel Since the plugin details shows only the version (6.0.0), there is no way to determine from which build this came. We really need this ability back. -- 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

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-689) Needs to be some indication to user that a data source needs to be created

by John Verhaeg (JIRA)

Needs to be some indication to user that a data source needs to be created -------------------------------------------------------------------------- Key: TEIIDDES-689 URL: https://jira.jboss.org/browse/TEIIDDES-689 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Affects Versions: 7.1 Reporter: John Verhaeg After creating one or more models and putting them in a VDB, there is no indication that the user needs to have a corresponding data source available on the server before they can successfully deploy that VDB. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-968) Catalog and Schema should use different icons so that they can be distinquished as to their type

by Van Halbert (JIRA)

Catalog and Schema should use different icons so that they can be distinquished as to their type ------------------------------------------------------------------------------------------------ Key: TEIIDDES-968 URL: https://issues.jboss.org/browse/TEIIDDES-968 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Affects Versions: 7.1.1 Reporter: Van Halbert Priority: Minor The catalog and schema should use different icons so that they can be distinguishable in the tree. The mouse-over type would also be helpful. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
17
0 / 0

[JBoss JIRA] Created: (TEIIDDES-960) StringNameValidator.createUniqueName() method is performing multiple unnecessary string operations

by Barry LaFond (JIRA)

StringNameValidator.createUniqueName() method is performing multiple unnecessary string operations -------------------------------------------------------------------------------------------------- Key: TEIIDDES-960 URL: https://issues.jboss.org/browse/TEIIDDES-960 Project: Teiid Designer Issue Type: Bug Components: Import/Export, Modeling Affects Versions: 7.4 Reporter: Barry LaFond Assignee: Dan Florian Fix For: 7.4 Discovered that StringNameValidator.createUniqueName() method is performing an interative existingName.toUpperCase() call. Importing BQT2 tables from SQL Server, for instance resulted in 2200+ calls to existingName.toUpperCase(). jdbc:sqlserver://slntdb02.mw.lab.eng.bos.redhat.com:1433;databaseName=bqt2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
9
0 / 0

[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

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-69) redundent model support properties should be removed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-69?page=com.atlassian.jira.plugi... ] Barry LaFond resolved TEIIDDES-69. ---------------------------------- Assignee: Barry LaFond Fix Version/s: 7.5 (was: Future) Resolution: Done This was completed as part of TEIIDDES-126 > redundent model support properties should be removed > ---------------------------------------------------- > > Key: TEIIDDES-69 > URL: https://issues.jboss.org/browse/TEIIDDES-69 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Minor > Fix For: 7.5 > > > Defect Tracker #23781: The model properties 'Set Criteria Max Size', Supports "Distinct', Supports "Join", Supports "Order By", and Supports "Outer Join" should be removed. These are all enforced by connector capabilities.be removed from mmquery in 5.0.3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-996) Create Web Service fails if the model contains 2 schemas with the same tablenames underneath

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-996?page=com.atlassian.jira.plug... ] Ted Jones updated TEIIDDES-996: ------------------------------- Workaround Description: Multiple workarounds: 1. Generate the web service models individually instead of at the model level. This will allow you to make the output view and schemas unigue in the "create web service" wizard. 2. In order to keep both schemas underneath the same model all the tablenames in the second schema would need to be changed. This isn't a viable solution though if the models contain numerous tables with the same name. was:In order to keep both schemas underneath the same model all the tablenames in the second schema would need to be changed. This isn't a viable solution though if the models contain numerous tables with the same name. > Create Web Service fails if the model contains 2 schemas with the same tablenames underneath > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-996 > URL: https://issues.jboss.org/browse/TEIIDDES-996 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Ted Jones > Labels: eds > Fix For: 7.5 > > > In Teiid Designer, if you import a Source Model that contains 2 schemas, each schema contains tables with the same name. Right-click > Modeling > Create Web Service fails: > "The name table_a_OutputView is the same (ignoring case) as 1 other object(s) under the same parent." > The default names for the table Output Views should also contain the schema/folder names, i.e. schemaA_tableA_OutputView. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 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 June 2011