September 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-1082) Model Extension Definitions (MEDs) Need To Be Marked As Either Built-in Or User-Defined

by Dan Florian (JIRA)

Model Extension Definitions (MEDs) Need To Be Marked As Either Built-in Or User-Defined ---------------------------------------------------------------------------------------- Key: TEIIDDES-1082 URL: https://issues.jboss.org/browse/TEIIDDES-1082 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.5 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.6 MEDs contributed via an Eclipse extension are built-in and cannot be removed/unregistered from the Model Extension Registry. However, user-defined MEDs are contributed by users and can be unregistered. In the current MED implementation there is no way to tell if it is built-in or user-defined. The Model Extension Registry View will have the ability to unregister MEDs so it needs to be able to find out which type of MED it is. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1072) can not edit REST extension properties,

by Frank Sauer (JIRA)

can not edit REST extension properties, ---------------------------------------- Key: TEIIDDES-1072 URL: https://issues.jboss.org/browse/TEIIDDES-1072 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.5 Reporter: Frank Sauer After REST enabling a procedure in 7.5RC1 the properties view shows the extension properties for REST but you can not set them. They immediately change back to blank. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1086) Relational Tables Text Import option is incomplete. Need a better flexible solution to import any relational model object and property

by Barry LaFond (JIRA)

Relational Tables Text Import option is incomplete. Need a better flexible solution to import any relational model object and property -------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1086 URL: https://issues.jboss.org/browse/TEIIDDES-1086 Project: Teiid Designer Issue Type: Bug Components: Import/Export, Modeling Affects Versions: 7.4 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker The CSV formatted Relational Tables option in the Text File importer is incomplete and buggy. We need to rethink and improve our text-file mechanism for importing ALL relational model objects including any of their supported relational properties. Propose using an XML-structure instead of CSV. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

6
40
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-1087) Teiid Designer randomly changes column names within transformations when migrating legacy MetaMatrix .xmi files

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1087?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1087. ------------------------------------- Resolution: Done I have updated the migration document at https://docspace.corp.redhat.com/docs/DOC-58202 to include the 'prepare' step in MMx 5.5.4, prior to doing the migration. > Teiid Designer randomly changes column names within transformations when migrating legacy MetaMatrix .xmi files > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1087 > URL: https://issues.jboss.org/browse/TEIIDDES-1087 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Priority: Critical > Fix For: 7.4.2 > > > Customer is using JBDS 4.1 (Teiid Designer 7.4) and is migrating his legacy MetaMatrix models (attached his 554Model project set). And have seen strange things: > 1) In a VBL layer, the SQL transformation dropped the _PL reference to the Physical (source) layer. In another VBL layer, the middle part of the PL table name was simply gone. > 2) A table named STATE_ALPHA_CD in the source models (PL) was changed in the SQL transform at the VBL to STATE_ALPHA_Code. > 3) In Plans_VML, a field named 'Baseline_Text' was changed in two queries to ULN_POC_NAME which naturally did not exist in the source tables of the transformation. > 4) In at least one query, the name of the layer was changed...instead of Transportation_VML, it appeared in the SQL transformation of the query as Transportation_Procs_VML. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-979) Add to the documentation what metadata used in designer has a material impact on runtime

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-979?page=com.atlassian.jira.plug... ] Van Halbert updated TEIIDDES-979: --------------------------------- Priority: Critical (was: Major) > Add to the documentation what metadata used in designer has a material impact on runtime > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-979 > URL: https://issues.jboss.org/browse/TEIIDDES-979 > Project: Teiid Designer > Issue Type: Enhancement > Components: Documentation > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Fix For: 7.4.2 > > > Add to the documentation what metadata used in designer has a material impact on runtime -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-1087) Teiid Designer randomly changes column names within transformations when migrating legacy MetaMatrix .xmi files

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1087?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1087: -------------------------------------- Assignee: Mark Drilling (was: Van Halbert) > Teiid Designer randomly changes column names within transformations when migrating legacy MetaMatrix .xmi files > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1087 > URL: https://issues.jboss.org/browse/TEIIDDES-1087 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Priority: Critical > Fix For: 7.4.2 > > > Customer is using JBDS 4.1 (Teiid Designer 7.4) and is migrating his legacy MetaMatrix models (attached his 554Model project set). And have seen strange things: > 1) In a VBL layer, the SQL transformation dropped the _PL reference to the Physical (source) layer. In another VBL layer, the middle part of the PL table name was simply gone. > 2) A table named STATE_ALPHA_CD in the source models (PL) was changed in the SQL transform at the VBL to STATE_ALPHA_Code. > 3) In Plans_VML, a field named 'Baseline_Text' was changed in two queries to ULN_POC_NAME which naturally did not exist in the source tables of the transformation. > 4) In at least one query, the name of the layer was changed...instead of Transportation_VML, it appeared in the SQL transformation of the query as Transportation_Procs_VML. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-1087) Teiid Designer randomly changes column names within transformations when migrating legacy MetaMatrix .xmi files

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1087?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1087: ----------------------------------- Fix Version/s: 7.4.2 Priority: Critical (was: Major) > Teiid Designer randomly changes column names within transformations when migrating legacy MetaMatrix .xmi files > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1087 > URL: https://issues.jboss.org/browse/TEIIDDES-1087 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Van Halbert > Priority: Critical > Fix For: 7.4.2 > > > Customer is using JBDS 4.1 (Teiid Designer 7.4) and is migrating his legacy MetaMatrix models (attached his 554Model project set). And have seen strange things: > 1) In a VBL layer, the SQL transformation dropped the _PL reference to the Physical (source) layer. In another VBL layer, the middle part of the PL table name was simply gone. > 2) A table named STATE_ALPHA_CD in the source models (PL) was changed in the SQL transform at the VBL to STATE_ALPHA_Code. > 3) In Plans_VML, a field named 'Baseline_Text' was changed in two queries to ULN_POC_NAME which naturally did not exist in the source tables of the transformation. > 4) In at least one query, the name of the layer was changed...instead of Transportation_VML, it appeared in the SQL transformation of the query as Transportation_Procs_VML. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-1087) Teiid Designer randomly changes column names within transformations when migrating legacy MetaMatrix .xmi files

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1087?page=com.atlassian.jira.plu... ] Van Halbert moved SOA-3424 to TEIIDDES-1087: -------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise SOA Platform) Key: TEIIDDES-1087 (was: SOA-3424) Affects Version/s: 7.4.2 (was: 5.1.0 GA) Component/s: (was: EDS) Security: (was: JBoss Internal) > Teiid Designer randomly changes column names within transformations when migrating legacy MetaMatrix .xmi files > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1087 > URL: https://issues.jboss.org/browse/TEIIDDES-1087 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Van Halbert > > Customer is using JBDS 4.1 (Teiid Designer 7.4) and is migrating his legacy MetaMatrix models (attached his 554Model project set). And have seen strange things: > 1) In a VBL layer, the SQL transformation dropped the _PL reference to the Physical (source) layer. In another VBL layer, the middle part of the PL table name was simply gone. > 2) A table named STATE_ALPHA_CD in the source models (PL) was changed in the SQL transform at the VBL to STATE_ALPHA_Code. > 3) In Plans_VML, a field named 'Baseline_Text' was changed in two queries to ULN_POC_NAME which naturally did not exist in the source tables of the transformation. > 4) In at least one query, the name of the layer was changed...instead of Transportation_VML, it appeared in the SQL transformation of the query as Transportation_Procs_VML. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-1085) Teiid Designer "Import Metadata from Text files on file system" in JBDS 4.1 no longer imports Datatypes

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1085?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1085. ------------------------------------ Resolution: Done Fixed datatype static initializer in RelationalTypeMappingImpl > Teiid Designer "Import Metadata from Text files on file system" in JBDS 4.1 no longer imports Datatypes > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1085 > URL: https://issues.jboss.org/browse/TEIIDDES-1085 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Priority: Blocker > Fix For: 7.4.2 > > > Using Teiid Designer inside of Developer Studio 4.1, importing the attach file in the "Import Metadata from Text files on file system" sets all the Columns datatypes to Object, when they are specified as INTEGER and VARCHAR in the file. This exact same file imports correctly in Developer Studio 4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-992) Allow the use of pushdown functions without requiring Java programming

by Bernd Groh (JIRA)

Allow the use of pushdown functions without requiring Java programming ---------------------------------------------------------------------- Key: TEIIDDES-992 URL: https://issues.jboss.org/browse/TEIIDDES-992 Project: Teiid Designer Issue Type: Feature Request Reporter: Bernd Groh Currently, in order to use a database function, even if pushdown is required, it is still necessary to add the function interface to a Java class within the connector, and the connector then must be deployed to the server in order to allow for this pushdown function to be used within the Designer. This creates a lot of extra effort every time you want to make use of a new database function. Particularly, given the schema designer doesn't necessarily have access to either the connector code or the server, and then must involve other parties simply to be able to use an additional database function. It would be very beneficial to speedy schema development if that was not necessary, and if, say, the interface could be defined on the Designer side, added to the VDB, and then deployed as part of the VDB. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

6
47
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2011