December 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3169) Missing native tag in Teiid Importer

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3169?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3169: ----------------------------------- Description: Teiid importer doesn't add the NATIVE tag to VDB content. Same problem as Van described [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...]. I use jdg7.1-remote-cache quick start from server. I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error: {code:java} 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata, 1) Define "importer.ProtoFilePath" to read from a local .proto file. 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly. 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file {code} I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png) was: Teiid importer doesn't add the NATIVE tag to VDB content. Same problem as Van describe [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...]. I use jdg7.1-remote-cache quick start from server. I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error: {code:java} 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata, 1) Define "importer.ProtoFilePath" to read from a local .proto file. 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly. 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file {code} I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png) > Missing native tag in Teiid Importer > ------------------------------------ > > Key: TEIIDDES-3169 > URL: https://issues.jboss.org/browse/TEIIDDES-3169 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Priority: Critical > Attachments: VDBcontent.png, dataSource.png, translator.png > > > Teiid importer doesn't add the NATIVE tag to VDB content. > Same problem as Van described [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...]. > I use jdg7.1-remote-cache quick start from server. > I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error: > {code:java} > 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata, > 1) Define "importer.ProtoFilePath" to read from a local .proto file. > 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly. > 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file > {code} > I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3169) Missing native tag in Teiid Importer

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-3169: -------------------------------------- Summary: Missing native tag in Teiid Importer Key: TEIIDDES-3169 URL: https://issues.jboss.org/browse/TEIIDDES-3169 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 11.1.1 Reporter: Matej Kralik Priority: Critical Attachments: VDBcontent.png, dataSource.png, translator.png Teiid importer doesn't add the NATIVE tag to VDB content. Same problem as Van describe [here|https://issues.jboss.org/browse/TEIIDDES-3084?focusedCommentId=13417...]. I use jdg7.1-remote-cache quick start from server. I have VDB and data source on the server, I choose this datasource (dataSource.png) and set translator to infinispan-hotrod (translator.png) but server shows error: {code:java} 15:22:00,121 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:TEIID25011 There are three ways to import the metadata, 1) Define "importer.ProtoFilePath" to read from a local .proto file. 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly. 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file {code} I noticed in the Advanced tab that NATIVE tag is missing. (VDBcontent.png) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3084) Support modeling of a JDG 7.1 data source using new translator/connector

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3084?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3084: ----------------------------------- Labels: release_notes (was: ) > Support modeling of a JDG 7.1 data source using new translator/connector > ------------------------------------------------------------------------ > > Key: TEIIDDES-3084 > URL: https://issues.jboss.org/browse/TEIIDDES-3084 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Labels: release_notes > Fix For: 11.1 > > Attachments: materialize-action.png, materialize-wizard-page-1-jdg-6.png, materialize-wizard-page-1-jdg-7.png, materialize-wizard-page-2-jdg-7.png, materialized-view-extension-props.png > > > Add the ability to model a JDG 7.1 data source using new Teiid connector/translator -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2939) Add module dependencies to support JDG 7.1 when Pojo is reversed engineered

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2939?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-2939. ---------------------------------- > Add module dependencies to support JDG 7.1 when Pojo is reversed engineered > --------------------------------------------------------------------------- > > Key: TEIIDDES-2939 > URL: https://issues.jboss.org/browse/TEIIDDES-2939 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Van Halbert > Assignee: Barry LaFond > Labels: release_notes > Fix For: 11.1 > > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2939) Add module dependencies to support JDG 7.1 when Pojo is reversed engineered

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2939?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-2939: ----------------------------------- Labels: release_notes (was: ) > Add module dependencies to support JDG 7.1 when Pojo is reversed engineered > --------------------------------------------------------------------------- > > Key: TEIIDDES-2939 > URL: https://issues.jboss.org/browse/TEIIDDES-2939 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Van Halbert > Assignee: Barry LaFond > Labels: release_notes > Fix For: 11.1 > > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3048) INSERT in source model with JDG as data source returns a Handling Results Sets problem dialog

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3048?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3048: ----------------------------------- Attachment: insertMultiValueJDG.png > INSERT in source model with JDG as data source returns a Handling Results Sets problem dialog > --------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3048 > URL: https://issues.jboss.org/browse/TEIIDDES-3048 > Project: Teiid Designer > Issue Type: Bug > Environment: MacOS > JBDS 10.3.0 > JBDSIS 10.0.2 > JDV 6.3.4 > JDG 6.6.1 > Reporter: Cojan van Ballegooijen > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: Screen Shot 2017-03-02 at 00.48.51.png, Screen Shot 2017-03-02 at 00.56.07.png, insertMultiValueJDG.png > > > When inserting rows from JBDS to a source model which is connected to a JDG data source it generate an Handling Result Sets problem dialog but the row is inserted into the cache. After clicking Ok. the next dialog hangs. You have to click Cancel to remove the dialog. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3048) INSERT in source model with JDG as data source returns a Handling Results Sets problem dialog

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3048?page=com.atlassian.jira.plu... ] Matej Kralik reopened TEIIDDES-3048: ------------------------------------ Insert one item works, but when I want to insert more items (insert four products from example -> Execute All), first insert passed but others failed due to: Cannot perform operations on a closed connection. (insertMultiValueJDG.png) > INSERT in source model with JDG as data source returns a Handling Results Sets problem dialog > --------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3048 > URL: https://issues.jboss.org/browse/TEIIDDES-3048 > Project: Teiid Designer > Issue Type: Bug > Environment: MacOS > JBDS 10.3.0 > JBDSIS 10.0.2 > JDV 6.3.4 > JDG 6.6.1 > Reporter: Cojan van Ballegooijen > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: Screen Shot 2017-03-02 at 00.48.51.png, Screen Shot 2017-03-02 at 00.56.07.png > > > When inserting rows from JBDS to a source model which is connected to a JDG data source it generate an Handling Result Sets problem dialog but the row is inserted into the cache. After clicking Ok. the next dialog hangs. You have to click Cancel to remove the dialog. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3163) Translator override properties can not be updated after re-generating a dynamic vdb

by Hiroki Daicho (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3163?page=com.atlassian.jira.plu... ] Hiroki Daicho reopened TEIIDDES-3163: ------------------------------------- > Translator override properties can not be updated after re-generating a dynamic vdb > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-3163 > URL: https://issues.jboss.org/browse/TEIIDDES-3163 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 11.1.1 > Environment: Devstudio 11.1.0 CR1 (Teiid Desinger 11.1.1) > Reporter: Hiroki Daicho > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: reproducer_project.zip > > > If dynamic vdb has already generated, Translator override properties can not be modified by regenerate dynamic vdb. > 1. Add Translator override property to vdb (testvdb.vdb). e.g. prop1 -> 100 > 2. generate dynamic vdb (testvdb-vdb.xml). > {code} > <property name="prop1" value="100"/> > {code} > 3. Modify the propery in vdb (testvdb.vdb). e.g. prop1 -> 199 > 4. generate dynamic vdb (testvdb-vdb.xml). > 5. the property is not updated to 199 in the dynamic vdb xml. > {code} > <property name="prop1" value="100"/> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3168) OData4 Imported MXD properties have a space

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3168?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3168: ---------------------------------------- [~rareddy] In debug I checked the info coming back from the server. The JSON from the CLI call for "allowed" property definition returned the json below. Which matches up with your odata 4 processor: https://github.com/teiid/teiid/blob/master/connectors/odata/translator-od... I think your allowed values string contains a space after each comma. Guess your string parser isn't trimming each value? allowed = "COMPLEX, NAVIGATION, ENTITY, ENTITY_COLLECTION, ACTION, FUNCTION, COMPLEX_COLLECTION, NAVIGATION_COLLECTION", {code} { "type" => STRING, "required" => true, "description" => "Type of OData Schema Item", "display" => "OData Type", "read-only" => false, "advanced" => false, "allowed" => [ "COMPLEX", " NAVIGATION", " ENTITY", " ENTITY_COLLECTION", " ACTION", " FUNCTION", " COMPLEX_COLLECTION", " NAVIGATION_COLLECTION" ], "masked" => false, "owner" => "org.teiid.metadata.Table,org.teiid.metadata.Procedure", "category" => "EXTENSION_METADATA" } {code} > OData4 Imported MXD properties have a space > ------------------------------------------- > > Key: TEIIDDES-3168 > URL: https://issues.jboss.org/browse/TEIIDDES-3168 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Priority: Critical > > The Metadata Extension Properties that are imported from server for OData4 translator have leading space in the definition, thus it creates a wrong VDB which fails to run during the runtime > {code} > <p:property advanced="false" index="true" masked="false" name="Type" required="true" type="string"> > <p:allowedValue>COMPLEX</p:allowedValue> > <p:allowedValue> NAVIGATION</p:allowedValue> > <p:allowedValue> COMPLEX_COLLECTION</p:allowedValue> > <p:allowedValue> ENTITY_COLLECTION</p:allowedValue> > <p:allowedValue> NAVIGATION_COLLECTION</p:allowedValue> > <p:allowedValue> ENTITY</p:allowedValue> > <p:allowedValue> FUNCTION</p:allowedValue> > <p:allowedValue> ACTION</p:allowedValue> > </p:property> > {code} > see allowed Values with leading white space. I am not sure this is how the server is providing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3034) Importing Virtual Procedure DDL containing a simple RETURNS type add a Result Set to procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3034?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3034. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/76798701a5f333eb5... Added check parameter properties and create a result set if a parameter has a result = TRUE value. > Importing Virtual Procedure DDL containing a simple RETURNS type add a Result Set to procedure > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3034 > URL: https://issues.jboss.org/browse/TEIIDDES-3034 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.1, 11.1 > > Attachments: viewModelFromComment.png, viewModelFromDescription.png > > > testing and debugging for TEIIDDES-2783 exposed an issue when importing a procedure containing a RETURNS data type and no result set. > The transformation resolving framework contains logic that will auto-create a result set containing a generated column. > We need to catch this use-case and prevent the result set from being created using this simple DDL input > {code} > CREATE VIRTUAL PROCEDURE ProcedureWithRS ( > stringIN string(4000) OPTIONS(ANNOTATION 'parameter 1 description') > ) RETURNS string(255) OPTIONS(ANNOTATION 'Example') AS > BEGIN > SELECT stringIN AS result; > END > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

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 2017