June 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-62) OpenApi 3.0 Support for OData

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-62?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-62. --------------------------------- Resolution: Done Support provided in Teiid 12.2.1 and 12.3.0 > OpenApi 3.0 Support for OData > ----------------------------- > > Key: TEIIDSB-62 > URL: https://issues.jboss.org/browse/TEIIDSB-62 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Support OpenAPI 3.0 document generation with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5763) GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5763?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5763: --------------------------------------- > I checked the documentation. but I could not find anything about this "key" variable. Is it a special variable like OLD and NEW? And for what is it good for in general? More use cases involved I should know of? As you guessed it should documented on: http://teiid.github.io/teiid-documents/master/content/reference/Update_Pr... However there was a typo on https://github.com/teiid/teiid-documents/blame/12.0.x/reference/Update_Pr... such that the example block was not closed properly and the content after that was not rendered. This is corrected now. It is specific to the generated key case. Since it is generally difficult to automatically determine the key value from a static analysis of the insert and it may not be correct to simply access the last generated key (in the case of a cascaded insert), we instead expect the procedure writer to explicitly set the key value. > Please give me an explanation for the key variable, at the moment it looks like magic to me Think of it as an implicit OUT variable. You can move it before the insert in your case because the value, vIdProduct, is already determined. > Shall I add a further jira issue to enhance the documentation in respect to the topic? The correction was checked in under this issue. > GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files > ----------------------------------------------------------------------------- > > Key: TEIID-5763 > URL: https://issues.jboss.org/browse/TEIID-5763 > Project: Teiid > Issue Type: Bug > Affects Versions: 12.2 > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Blocker > > The issue arrised in: > https://developer.jboss.org/message/989700#989700 > Following sceanarios are given: > Variant 1: > Table Product(id), primary key = autoincrement; > Table QuicklyAddedProduct, primary key is foreign key on Product.id > Table Diary_SRC > View Diary on Diary_SRC > INSTEAD OF INSERT Trigger on Diary should : > -create new record on Product, > -get autoincremented Product.id of new record, > - create new QuicklyAddedProduct with returned Product.id as primary key > - create new Diary record with QuicklyAddedProduct > { > INSERT a new record on Product; > idProduct = CONVERT(GENERATED_KEY('idProduct'),long); // fails > } > Variant 2: > INSTEAD OF INSERT trigger on Diary should : > - create new QuicklyAddedProduct > - add Quickly added prodcut to Diary > additionally a INSTEAD OF trigger on QuicklyAddedProduct exists which: > - creates new Product record > - uses returned GENERATED_KEY(Product.id) to add record on QuicklyAddedProduct with Product.id as primary key -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5763) GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5763?page=com.atlassian.jira.plugin... ] Christoph John commented on TEIID-5763: --------------------------------------- Hello Steven, thank you very much, I would have never found this solution !!! I checked the documentation. but I could not find anything about this "key" variable. Is it a special variable like OLD and NEW? And for what is it good for in general? More use cases involved I should know of? Seems it does not matter if I move key.fkProduct = vIdProduct before INSERT INTO QuicklyAddedProducts_SRC(...) or not. Please give me an explanation for the key variable, at the moment it looks like magic to me :) Shall I add a further jira issue to enhance the documentation in respect to the topic? Would be great to have the key described and a simple example like the one we just addressed. I assume others will run into this issue as well. Good place might be http://teiid.github.io/teiid-documents/12.0.x/content/reference/Update_Pr... > GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files > ----------------------------------------------------------------------------- > > Key: TEIID-5763 > URL: https://issues.jboss.org/browse/TEIID-5763 > Project: Teiid > Issue Type: Bug > Affects Versions: 12.2 > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Blocker > > The issue arrised in: > https://developer.jboss.org/message/989700#989700 > Following sceanarios are given: > Variant 1: > Table Product(id), primary key = autoincrement; > Table QuicklyAddedProduct, primary key is foreign key on Product.id > Table Diary_SRC > View Diary on Diary_SRC > INSTEAD OF INSERT Trigger on Diary should : > -create new record on Product, > -get autoincremented Product.id of new record, > - create new QuicklyAddedProduct with returned Product.id as primary key > - create new Diary record with QuicklyAddedProduct > { > INSERT a new record on Product; > idProduct = CONVERT(GENERATED_KEY('idProduct'),long); // fails > } > Variant 2: > INSTEAD OF INSERT trigger on Diary should : > - create new QuicklyAddedProduct > - add Quickly added prodcut to Diary > additionally a INSTEAD OF trigger on QuicklyAddedProduct exists which: > - creates new Product record > - uses returned GENERATED_KEY(Product.id) to add record on QuicklyAddedProduct with Product.id as primary key -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5763) GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5763?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5763: --------------------------------------- An odata exception such as "{"error":{"code":null,"message":"TEIID16016 Insert into QuicklyAddedProducts success, but failed to retrieve auto generated keys from source, thus failed to show result entity; Supply the key values."}}" is what I was mentioning as issue 3. It requires that the key value is explicitly set: CREATE TRIGGER ON QuicklyAddedProducts INSTEAD OF INSERT AS FOR EACH ROW BEGIN ATOMIC DECLARE long vIdProduct; INSERT INTO Products(fkDatabaseKey) VALUES (2); vIdProduct = generated_key();--CONVERT(GENERATED_KEY('idProduct'),long); -- create a new record for the quickly added product INSERT INTO QuicklyAddedProducts_SRC(fkProduct, fkProfile, product_name, energy_100g, carbohydrates_100g, proteins_100g, fat_100g) VALUES (vIdProduct, new.fkProfile, new.product_name, new.energy_100g, new.carbohydrates_100g, new.proteins_100g, new.fat_100g); *key.fkProduct = vIdProduct;* END; And unintuitively for the view auto increment column to be not null: CREATE VIEW QuicklyAddedProducts (fkProduct long *NOT NULL* AUTO_INCREMENT ... After that things seem to work fine. I'll make another commit under this issue to not require the not null on the auto_increment. > GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files > ----------------------------------------------------------------------------- > > Key: TEIID-5763 > URL: https://issues.jboss.org/browse/TEIID-5763 > Project: Teiid > Issue Type: Bug > Affects Versions: 12.2 > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Blocker > > The issue arrised in: > https://developer.jboss.org/message/989700#989700 > Following sceanarios are given: > Variant 1: > Table Product(id), primary key = autoincrement; > Table QuicklyAddedProduct, primary key is foreign key on Product.id > Table Diary_SRC > View Diary on Diary_SRC > INSTEAD OF INSERT Trigger on Diary should : > -create new record on Product, > -get autoincremented Product.id of new record, > - create new QuicklyAddedProduct with returned Product.id as primary key > - create new Diary record with QuicklyAddedProduct > { > INSERT a new record on Product; > idProduct = CONVERT(GENERATED_KEY('idProduct'),long); // fails > } > Variant 2: > INSTEAD OF INSERT trigger on Diary should : > - create new QuicklyAddedProduct > - add Quickly added prodcut to Diary > additionally a INSTEAD OF trigger on QuicklyAddedProduct exists which: > - creates new Product record > - uses returned GENERATED_KEY(Product.id) to add record on QuicklyAddedProduct with Product.id as primary key -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5769) Provide a conversion from string to json

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5769: ------------------------------------- Summary: Provide a conversion from string to json Key: TEIID-5769 URL: https://issues.jboss.org/browse/TEIID-5769 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.3 For convenience there should be a conversion of string to json. This is complicated as we don't want to add too much into common-core, so we may need some reflective loading. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5767) Swagger metadata import does not account for undefined basePath

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5767?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5767. ----------------------------------- Resolution: Done Added a null check to the handling. > Swagger metadata import does not account for undefined basePath > --------------------------------------------------------------- > > Key: TEIID-5767 > URL: https://issues.jboss.org/browse/TEIID-5767 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > If the swagger document does not define the basepath you can end up with urls that contain null: > https://management.azure.comnull/providers/Microsoft.Cache/operations > Rather than the expected: > https://management.azure.com/providers/Microsoft.Cache/operations -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5767) Swagger metadata import does not account for undefined basePath

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5767: ------------------------------------- Summary: Swagger metadata import does not account for undefined basePath Key: TEIID-5767 URL: https://issues.jboss.org/browse/TEIID-5767 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.3 If the swagger document does not define the basepath you can end up with urls that contain null: https://management.azure.comnull/providers/Microsoft.Cache/operations Rather than the expected: https://management.azure.com/providers/Microsoft.Cache/operations -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5766) MongoDB import fails when collection contains an empty array

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5766?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5766. ----------------------------------- Fix Version/s: 12.3 Resolution: Done Added logic to skip the import logic for empty lists. > MongoDB import fails when collection contains an empty array > ------------------------------------------------------------ > > Key: TEIID-5766 > URL: https://issues.jboss.org/browse/TEIID-5766 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.17.6_4 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > MongoDB import fails with error like [1] when collection returns an empty array in the first doc. > [1] > 14:32:38,167 WARN [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:Index: 0, Size: 0: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.rangeCheck(ArrayList.java:657) [rt.jar:1.8.0_171] > at java.util.ArrayList.get(ArrayList.java:433) [rt.jar:1.8.0_171] > at org.teiid.translator.mongodb.MongoDBMetadataProcessor.addColumn(MongoDBMetadataProcessor.java:149) > at org.teiid.translator.mongodb.MongoDBMetadataProcessor.addTable(MongoDBMetadataProcessor.java:115) > at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:72) > at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:48) > at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:950) [teiid-api-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] > at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] > at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] > at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5766) MongoDB import fails when collection contains an empty array

by Marc Shirley (Jira)

Marc Shirley created TEIID-5766: ----------------------------------- Summary: MongoDB import fails when collection contains an empty array Key: TEIID-5766 URL: https://issues.jboss.org/browse/TEIID-5766 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.12.17.6_4 Reporter: Marc Shirley Assignee: Steven Hawkins MongoDB import fails with error like [1] when collection returns an empty array in the first doc. [1] 14:32:38,167 WARN [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50036 VDB importVDB.1 model "importVDBSrcModel" metadata failed to load. Reason:Index: 0, Size: 0: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:657) [rt.jar:1.8.0_171] at java.util.ArrayList.get(ArrayList.java:433) [rt.jar:1.8.0_171] at org.teiid.translator.mongodb.MongoDBMetadataProcessor.addColumn(MongoDBMetadataProcessor.java:149) at org.teiid.translator.mongodb.MongoDBMetadataProcessor.addTable(MongoDBMetadataProcessor.java:115) at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:72) at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:48) at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:950) [teiid-api-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) [teiid-engine-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) [teiid-engine-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.17.6_4-redhat-64-2.jar:8.12.17.6_4-redhat-64-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] at org.jboss.threads.JBossThread.run(JBossThread.java:122) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-107) Update Teiid version to 12.2.1

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-107?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-107: --------------------------------- Fix Version/s: (was: 1.2.0) > Update Teiid version to 12.2.1 > ------------------------------ > > Key: TEIIDSB-107 > URL: https://issues.jboss.org/browse/TEIIDSB-107 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 7.4-1.1.1 > > > Update the Teiid version to 12.2.1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2019