March 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2800) Add back New Child >>View option to the View Model

by wayne zimmerman (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2800?page=com.atlassian.jira.plu... ] wayne zimmerman commented on TEIIDDES-2800: ------------------------------------------- To clarify the request (which is actually 2 requests): Request #1: The New Child menu in a source model has the option to create a View (in addition to Table, Procedure, Index, etc.), but this option does not appear in a view model (only options are Table, Procedure, Index). So, the request is to add the View option (to the New Child menu for a view model). The reason why this is important: If one uses the New Model Wizard to create a source model where the underlying objects are database views, then the wizard creates relational views. Subsequently, when one creates a view model based on the source model, it also creates relational views. If more database views are subsequently added to the database, then that impacts both the source and view models. You can manually add a relational view to the source model, but you can't add it to the view model, thus the reason for this request. Request #2: Add an option to the New Model wizard when creating a view model based on a source model that controls what type of object is created (either relational view or relational table), rather than creating the same type of object in the view model that exists in source model. So, I could have a source model consisting of relational views (corresponding to the underlying database views) and I could have a view model consisting of relational tables (corresponding to the relational views in the source model). There is no easy way to do this currently. > Add back New Child >>View option to the View Model > -------------------------------------------------- > > Key: TEIIDDES-2800 > URL: https://issues.jboss.org/browse/TEIIDDES-2800 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > > RFE https://issues.jboss.org/browse/TEIID-4010 has been entered to differentiate table and view, so would like to have New View and Table option under View Model > New Child. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2564) Add support to support comments in VDB XML manifest

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2564?page=com.atlassian.jira.plu... ] Matus Makovy edited comment on TEIIDDES-2564 at 3/2/16 10:00 AM: ----------------------------------------------------------------- I tried to verify this with portfolio-vdb.xml and TD didn't preserve the comments. I generated TD vdb (and models) from dynamic VDB and then once again generated dynamic vdb from TD vdb and the comments were not there. TD 10.0.0.Beta3 was (Author: mmakovy): I tried to verify this with portfolio-vdb.xml and TD didn't preserve the comments. I generated TD vdb (and models) from dynamic VDB and then once again generated dynamic vdb from TD vdb and the comments were not there. > Add support to support comments in VDB XML manifest > --------------------------------------------------- > > Key: TEIIDDES-2564 > URL: https://issues.jboss.org/browse/TEIIDDES-2564 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, VDB & Execution > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 10.0.1, 9.2.1 > > > Dynamic VDBs are XML files that supports general comments. We need to make sure that Designer's VDB Manifest business object supports reading and writing these comments. > This will be critical for the new import/export dynamic VDB features. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2564) Add support to support comments in VDB XML manifest

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2564?page=com.atlassian.jira.plu... ] Matus Makovy reopened TEIIDDES-2564: ------------------------------------ I tried to verify this with portfolio-vdb.xml and TD didn't preserve the comments. I generated TD vdb (and models) from dynamic VDB and then once again generated dynamic vdb from TD vdb and the comments were not there. > Add support to support comments in VDB XML manifest > --------------------------------------------------- > > Key: TEIIDDES-2564 > URL: https://issues.jboss.org/browse/TEIIDDES-2564 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, VDB & Execution > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 10.0.1, 9.2.1 > > > Dynamic VDBs are XML files that supports general comments. We need to make sure that Designer's VDB Manifest business object supports reading and writing these comments. > This will be critical for the new import/export dynamic VDB features. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2622) DDL importer does not properly set Materialized table options

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2622?page=com.atlassian.jira.plu... ] Matus Makovy reopened TEIIDDES-2622: ------------------------------------ I tried to import dynamic vdb with materialization table property set to existing table and the property was not set in newly generated model. > DDL importer does not properly set Materialized table options > ------------------------------------------------------------- > > Key: TEIIDDES-2622 > URL: https://issues.jboss.org/browse/TEIIDDES-2622 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export, ModeShape Integration, Patch Release > Affects Versions: 9.0.1, 9.1 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 10.0.1, 9.2.1 > > > Importing a DDL similar to the one [here|https://docs.jboss.org/author/display/teiid810final/External+Materia...], the Materialized property of the view table is set, but the Materialized Table property is not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2800) Add back New Child >>View option to the View Model

by Debbie Steigner (JIRA)

Debbie Steigner created TEIIDDES-2800: ----------------------------------------- Summary: Add back New Child >>View option to the View Model Key: TEIIDDES-2800 URL: https://issues.jboss.org/browse/TEIIDDES-2800 Project: Teiid Designer Issue Type: Feature Request Affects Versions: 9.2, 9.0.3 Reporter: Debbie Steigner RFE https://issues.jboss.org/browse/TEIID-4010 has been entered to differentiate table and view, so would like to have New View and Table option under View Model > New Child. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2427) Add Geometry Type

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2427?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2427. ---------------------------------- We have verified that this is included in TD 10.0.0.Beta3. There is a minor issue described here: TEIIDDES-2799. > Add Geometry Type > ----------------- > > Key: TEIIDDES-2427 > URL: https://issues.jboss.org/browse/TEIIDDES-2427 > Project: Teiid Designer > Issue Type: Feature Request > Components: ModeShape Integration, Patch Release, Teiid Integration > Reporter: luca gioppo > Assignee: Barry LaFond > Labels: release_notes, spatial, types, verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1, 9.2.1 > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > As part of TEIID-2384 a geometry type has been added to Teiid (blob + srid int) with associated system and pushdown logic. Designer should add support for the new type as well. We need to coordinate on the type uuid as that will bridge between Teiid and Designer. Currently Teiid just modified the blob identifier - https://github.com/teiid/teiid/blob/master/engine/src/main/resources/org/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2427) Add Geometry Type

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2427?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2427: ----------------------------------- Labels: release_notes spatial types verified_jbdsis-9.0.0.Beta (was: spatial types) > Add Geometry Type > ----------------- > > Key: TEIIDDES-2427 > URL: https://issues.jboss.org/browse/TEIIDDES-2427 > Project: Teiid Designer > Issue Type: Feature Request > Components: ModeShape Integration, Patch Release, Teiid Integration > Reporter: luca gioppo > Assignee: Barry LaFond > Labels: release_notes, spatial, types, verified_jbdsis-9.0.0.Beta > Fix For: 10.0.1, 9.2.1 > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > As part of TEIID-2384 a geometry type has been added to Teiid (blob + srid int) with associated system and pushdown logic. Designer should add support for the new type as well. We need to coordinate on the type uuid as that will bridge between Teiid and Designer. Currently Teiid just modified the blob identifier - https://github.com/teiid/teiid/blob/master/engine/src/main/resources/org/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2799) Import Geometry types

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-2799: -------------------------------------- Summary: Import Geometry types Key: TEIIDDES-2799 URL: https://issues.jboss.org/browse/TEIIDDES-2799 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 10.0.1 Reporter: Matej Kralik Attachments: screenshot1.png, screenshot2.png In the Maria DB I create tables with contain geometry type. Each table contains one of type(POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION, GEOMETRY)). When I generated source model from their, only geometry has been set geometry type (screenshot 1). The others have been set object type. I generate VDB and execute it. This query {code:java} SELECT ST_AsText(g) FROM gis_geometry {code} works only geometry type (screenshot 1). However when I set geometry type manually for all columns in source model, query works for all tables (screenshot 2). I think that Teiid Designer will should set geometry type for all this types when it import tables from JDBC source. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2720) Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2720?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2720: ---------------------------------------- This cannot be verified because of TEIIDDES-2798 > Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB > -------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2720 > URL: https://issues.jboss.org/browse/TEIIDDES-2720 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Import/Export, Patch Release, Web Services Support > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 10.0.1, 9.2.1 > > Attachments: export-dynamic-vdb-status-dialog.png > > > [~blafond]: > {quote}WS Operations are really just Virtual Procedures, so we could convert WS models in the near term{quote} > Exporting VDB with a web service model currently results in an empty model. Add the ability to export WS operations as virtual procedures. > Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2698) REST procedure in generated dynamic VDB does not work

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2698?page=com.atlassian.jira.plu... ] Matus Makovy resolved TEIIDDES-2698. ------------------------------------ Resolution: Done This is resolved, but it cannot be verified because of TEIIDDES-2798 > REST procedure in generated dynamic VDB does not work > ----------------------------------------------------- > > Key: TEIIDDES-2698 > URL: https://issues.jboss.org/browse/TEIIDDES-2698 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Extension Framework, VDB & Execution > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Fix For: 10.0.1, 9.2.1 > > Attachments: DynamicProcedureProject.zip > > > When a VDB containing view model with a REST procedure is exported as a dynamic VDB, the resulting autogenrated WAR does not work. This is because the generated DDL does not contain the OPTIONS clause with REST properties, nor does it contain the required SET NAMESPACE statement > Generated DDL: > {code:sql} > CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) > AS > BEGIN > SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; > END; > {code} > Expected DDL (note that this also incorporates TEIIDDES-2697): > {code:sql} > SET NAMESPACE 'http://teiid.org/rest' AS REST; > CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}') > AS > BEGIN > SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; > END; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2016