December 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2741) Concatenation operator || incompatible with import SQL

by Jean-Pierre Matsumoto (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2741?page=com.atlassian.jira.plu... ] Jean-Pierre Matsumoto updated TEIIDDES-2741: -------------------------------------------- Attachment: 2015-12-01_14-19-28.png > Concatenation operator || incompatible with import SQL > ------------------------------------------------------ > > Key: TEIIDDES-2741 > URL: https://issues.jboss.org/browse/TEIIDDES-2741 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 9.0.3 > Environment: Windows 7 64-bit > JBoss Studio 8.1.0 > Teiid Designer 9.0.3 > Reporter: Jean-Pierre Matsumoto > Attachments: 2015-12-01_14-19-28.png > > > When an SQL transformation contains concatenation operator ||, it cannot be imported. Error raised is: Problem importing the transformation SQL from a file. 2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2741) Concatenation operator || incompatible with import SQL

by Jean-Pierre Matsumoto (JIRA)

Jean-Pierre Matsumoto created TEIIDDES-2741: ----------------------------------------------- Summary: Concatenation operator || incompatible with import SQL Key: TEIIDDES-2741 URL: https://issues.jboss.org/browse/TEIIDDES-2741 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 9.0.3 Environment: Windows 7 64-bit JBoss Studio 8.1.0 Teiid Designer 9.0.3 Reporter: Jean-Pierre Matsumoto When an SQL transformation contains concatenation operator ||, it cannot be imported. Error raised is: Problem importing the transformation SQL from a file. 2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2740) JDBC Importer process should handle when the metadata not available

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2740: ------------------------------------- Summary: JDBC Importer process should handle when the metadata not available Key: TEIIDDES-2740 URL: https://issues.jboss.org/browse/TEIIDDES-2740 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 9.2 Reporter: Van Halbert The JDBC importer process should better handle when the metadata isn't provided by the driver. Instead of a NPE, maybe a message should be presented indicating that the metadata isn't being presented by the driver, please check your access rights to the database metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2401. ---------------------------------- This is included in TD 9.0.4., but we have found a couple of issues with dynamic VDB import/export - see TEIIDDES-2699 > 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 > Priority: Blocker > Labels: release_notes, verified_jbdsis-8.0.4.CR3 > Fix For: 9.0.4, 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.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2343) Support importing Dynamic VDB

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2343?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2343. ---------------------------------- This is included in TD 9.0.4., but we have found a couple of issues with dynamic VDB import/export - see TEIIDDES-2699 > Support importing Dynamic VDB > ----------------------------- > > Key: TEIIDDES-2343 > URL: https://issues.jboss.org/browse/TEIIDDES-2343 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Labels: release_notes, verified_jbdsis-8.0.4.CR3 > Fix For: 9.0.4, 9.2 > > Attachments: generate-vdb-archive-page-1.png, generate-vdb-archive-page-2.png > > > There should be an import option that supports importing a dynamic VDB. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2401: ----------------------------------- Labels: release_notes verified_jbdsis-8.0.4.CR3 (was: ) > 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 > Priority: Blocker > Labels: release_notes, verified_jbdsis-8.0.4.CR3 > Fix For: 9.0.4, 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.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2343) Support importing Dynamic VDB

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2343?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2343: ----------------------------------- Labels: release_notes verified_jbdsis-8.0.4.CR3 (was: ) > Support importing Dynamic VDB > ----------------------------- > > Key: TEIIDDES-2343 > URL: https://issues.jboss.org/browse/TEIIDDES-2343 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Labels: release_notes, verified_jbdsis-8.0.4.CR3 > Fix For: 9.0.4, 9.2 > > Attachments: generate-vdb-archive-page-1.png, generate-vdb-archive-page-2.png > > > There should be an import option that supports importing a dynamic VDB. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2015