August 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1995) Add templates for OBJECTTABLE, TEXTABLE, etc

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1995?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1995: ----------------------------------- Fix Version/s: 9.2 9.0.4 > Add templates for OBJECTTABLE, TEXTABLE, etc > -------------------------------------------- > > Key: TEIIDDES-1995 > URL: https://issues.jboss.org/browse/TEIIDDES-1995 > Project: Teiid Designer > Issue Type: Enhancement > Components: Transformations > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 9.2, 9.0.4 > > > Add templates for using OBJECTTABLE, TEXTTABLE, etc. to the the list of templates to apply to the transformation. Example: > SELECT > o.{colname}, o.{colname} > FROM > {ObjectTableName} as T, > OBJECTTABLE('x' PASSING T.{ObjectColumnName}Object as x COLUMNS > {colname} type 'teiid_row.{colname}', ….) as o -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2610) Add some default values to importer properties in Teiid Connection Importer

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2610: -------------------------------------- Summary: Add some default values to importer properties in Teiid Connection Importer Key: TEIIDDES-2610 URL: https://issues.jboss.org/browse/TEIIDDES-2610 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 9.1 Reporter: Barry LaFond Fix For: 9.2 Importing JDBC sources via Teiid Connection importer can be streamlined by providing/setting certain default import property values. 2 such properties are: *Table Types* > *TABLE* *use Qualified Name* > *false* This will help in the most common use-case to reduce the number of steps to importer and improve the experience of first-time users. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2401: -------------------------------------- Assignee: Barry LaFond > Add support exporting the Designer VDB as Dynamic VDB > ----------------------------------------------------- > > Key: TEIIDDES-2401 > URL: https://issues.jboss.org/browse/TEIIDDES-2401 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 9.2 > > Attachments: generate-dynamic-vdb-page-1.png > > > When a VDB is developed in the Designer, provide an option to export the given VDB as Dynamic VDB, which is simple XML format using DDL. > The server already provides mechanism to retrieve the schema (DDL) for a given model. Using this technique of retrieving the DDL, this feature can be built. > One caveat is support for XML document models in Dynamic VDB. When VDB contains XML document model, do not support this feature. > This has couple benefits > * Users can use these in Teiid for simplified usage. > * Can used to check the models into source repository like GIT or SVN etc and compare with later versions for modifications > * Open Shift > As for importing of Dynamic VDB, that can be handled as separate issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2401: ----------------------------------- Fix Version/s: 9.2 > Add support exporting the Designer VDB as Dynamic VDB > ----------------------------------------------------- > > Key: TEIIDDES-2401 > URL: https://issues.jboss.org/browse/TEIIDDES-2401 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Ramesh Reddy > Fix For: 9.2 > > Attachments: generate-dynamic-vdb-page-1.png > > > When a VDB is developed in the Designer, provide an option to export the given VDB as Dynamic VDB, which is simple XML format using DDL. > The server already provides mechanism to retrieve the schema (DDL) for a given model. Using this technique of retrieving the DDL, this feature can be built. > One caveat is support for XML document models in Dynamic VDB. When VDB contains XML document model, do not support this feature. > This has couple benefits > * Users can use these in Teiid for simplified usage. > * Can used to check the models into source repository like GIT or SVN etc and compare with later versions for modifications > * Open Shift > As for importing of Dynamic VDB, that can be handled as separate issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2399) Creating view model from source model with generate transformations results in orphaned annotated object reference to source

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2399?page=com.atlassian.jira.plu... ] Andrej Šmigala updated TEIIDDES-2399: ------------------------------------- Labels: release_notes verified_jbdsis-8.0.3.CR2 (was: ) > Creating view model from source model with generate transformations results in orphaned annotated object reference to source > ---------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2399 > URL: https://issues.jboss.org/browse/TEIIDDES-2399 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.3.CR2 > Fix For: 9.0.3, 9.2 > > > Create a View model from a source model and choose the "Transform.." option to generate default transformations. > The resulting View model will contain an extra <annotatedObject> reference in the same <annotations> element as the *relational* extension model reference > {code:xml} > <mmcore:AnnotationContainer xmi:uuid="mmuuid:9c7ac03c-bafc-4aa1-855f-4e6a43dd9c21"> > <annotations xmi:uuid="mmuuid:7aeb8904-fe0c-42ac-ae67-72c8ce5b397d"> > <tags xmi:uuid="mmuuid:873b6c71-41d4-476a-bf9a-442cb7fd7943" key="modelExtensionDefinition:relational" value="relational"/> > <annotatedObject href="XXXXXXX.xmi#mmuuid/7291fb4c-da39-4bbc-9787-d2edd9b9551c"/> > </annotations> > {code} > This won't cause problems for the View model, however if the View model is copied to yet another view model, the Model Import for the original source model will end up in the top level view model due to the orphaned "href=....." -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2399) Creating view model from source model with generate transformations results in orphaned annotated object reference to source

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2399?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2399. ------------------------------------ > Creating view model from source model with generate transformations results in orphaned annotated object reference to source > ---------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2399 > URL: https://issues.jboss.org/browse/TEIIDDES-2399 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.3.CR2 > Fix For: 9.0.3, 9.2 > > > Create a View model from a source model and choose the "Transform.." option to generate default transformations. > The resulting View model will contain an extra <annotatedObject> reference in the same <annotations> element as the *relational* extension model reference > {code:xml} > <mmcore:AnnotationContainer xmi:uuid="mmuuid:9c7ac03c-bafc-4aa1-855f-4e6a43dd9c21"> > <annotations xmi:uuid="mmuuid:7aeb8904-fe0c-42ac-ae67-72c8ce5b397d"> > <tags xmi:uuid="mmuuid:873b6c71-41d4-476a-bf9a-442cb7fd7943" key="modelExtensionDefinition:relational" value="relational"/> > <annotatedObject href="XXXXXXX.xmi#mmuuid/7291fb4c-da39-4bbc-9787-d2edd9b9551c"/> > </annotations> > {code} > This won't cause problems for the View model, however if the View model is copied to yet another view model, the Model Import for the original source model will end up in the top level view model due to the orphaned "href=....." -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2609) Support Enterprise Data Type Aliasing in Komodo

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2609: ------------------------------------- Summary: Support Enterprise Data Type Aliasing in Komodo Key: TEIIDDES-2609 URL: https://issues.jboss.org/browse/TEIIDDES-2609 Project: Teiid Designer Issue Type: Feature Request Components: komodo-common Reporter: Van Halbert Provide the ability to support enterprise data type aliasing that maps to the Teiid runtime data types. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Andrej Šmigala updated TEIIDDES-2460: ------------------------------------- Attachment: TEIIDDES2460.zip > JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2460 > URL: https://issues.jboss.org/browse/TEIIDDES-2460 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 9.0.3, 9.2 > > Attachments: ErrorDialog.png, TEIIDDES2460.zip > > > When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised > Version-Release number of selected component (if applicable): > Actual results: > Imported schema has changed integer data type to biginteger data type. > Expected results: > Imported schema will be identical to original schema. > Additional info: > Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Andrej Šmigala reopened TEIIDDES-2460: -------------------------------------- Importing with JDBC importer still changes integer to biginteger. It is no longer possible to create new models with the integer datatype (designer uses int instead). However, this might still be a problem if a user wants to import (reuse) from an older vdb created in previous versions of designer (one such vdb is attached). Steps to reproduce in current designer: # import the attached model # notice the table t1 in the source model has column c1 : integer # execute the vdb # Import from JDBC, select the vdb connection profile, check "Import as VDB source model" # finish the import, notice the t1 table in the new model has column c1 : biginteger > JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2460 > URL: https://issues.jboss.org/browse/TEIIDDES-2460 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 9.0.3, 9.2 > > Attachments: ErrorDialog.png > > > When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised > Version-Release number of selected component (if applicable): > Actual results: > Imported schema has changed integer data type to biginteger data type. > Expected results: > Imported schema will be identical to original schema. > Additional info: > Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2580) Upgrade Modeshape jars to latest 3.8.x version

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2580?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2580. ---------------------------------- > Upgrade Modeshape jars to latest 3.8.x version > ---------------------------------------------- > > Key: TEIIDDES-2580 > URL: https://issues.jboss.org/browse/TEIIDDES-2580 > Project: Teiid Designer > Issue Type: Task > Components: Build > Reporter: Barry LaFond > Assignee: Dan Florian > Labels: release_notes, verified_jbdsis-8.0.3.CR2 > Fix For: 9.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 August 2015