June 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-108) Add support for swagger/openapi sources

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-108?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-108: -------------------------------------- IMO I do not think we need to support those explicitly, generic web service support will handle as a catch-all. > Add support for swagger/openapi sources > --------------------------------------- > > Key: TEIIDSB-108 > URL: https://issues.jboss.org/browse/TEIIDSB-108 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > There should be source support for swagger/openapi. If we don't want swagger 1 support, then this can just add support for the openapi translator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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: --------------------------------------- > Does it always represent the key value of the table on which the last insert was done? It represents whatever the auto increment value for the view is, so v1.k in your example above - regardless of how many logical inserts you actually perform for that row of v1. > 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)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-108) Add support for swagger/openapi sources

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-108?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIIDSB-108: ---------------------------------------- No as in swagger versions prior to version 2. > Add support for swagger/openapi sources > --------------------------------------- > > Key: TEIIDSB-108 > URL: https://issues.jboss.org/browse/TEIIDSB-108 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > There should be source support for swagger/openapi. If we don't want swagger 1 support, then this can just add support for the openapi translator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 edited comment on TEIID-5763 at 6/17/19 5:32 PM: ---------------------------------------------------------------- Hello Steven, great. But I do have one further question regarding the key variable. Does it always represent the key value of the table on which the last insert was done? I mean, in case I have multiple inserts in an insert trigger on different tables, is then the key variable always associated with the record on the table of the last insert? for example: {code:java} CREATE FOREIGN TABLE tableA(i integer ,k integer not null auto_increment primary key); CREATE FOREIGN TABLE tableB(i integer ,k integer not null auto_increment primary key) CREATE FOREIGN TABLE tableC(i integer ,k integer not null auto_increment primary key) create view v1 (i integer, k integer not null auto_increment primary key) OPTIONS (UPDATABLE true) as select x, y from tableC; create trigger on v1 instead of insert as for each row begin atomic insert into tableA (i) values (new.i); --key.k references tableA.k? insert into tableB (i) values (new.i); --key.k references tableB.k? insert into tableC (i) values(new.i); --key.k references tableC.k? {code} was (Author: cjohn001): Hello Steven, great. But I do have one further question regarding the key variable. Does it always represent the key value of the table on which the last insert was done? I mean, in case I have multiple inserts in an insert trigger on different tables, is then the key variable always associated with the record on the table of the last insert? for example: CREATE FOREIGN TABLE tableA(i integer ,k integer not null auto_increment primary key); CREATE FOREIGN TABLE tableB(i integer ,k integer not null auto_increment primary key) CREATE FOREIGN TABLE tableC(i integer ,k integer not null auto_increment primary key) create view v1 (i integer, k integer not null auto_increment primary key) OPTIONS (UPDATABLE true) as select x, y from tableC; create trigger on v1 instead of insert as for each row begin atomic insert into tableA (i) values (new.i); --key.k references tableA.k? insert into tableB (i) values (new.i); --key.k references tableB.k? insert into tableC (i) values(new.i); --key.k references tableC.k? > 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)

6 years, 9 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 edited comment on TEIID-5763 at 6/17/19 5:31 PM: ---------------------------------------------------------------- Hello Steven, great. But I do have one further question regarding the key variable. Does it always represent the key value of the table on which the last insert was done? I mean, in case I have multiple inserts in an insert trigger on different tables, is then the key variable always associated with the record on the table of the last insert? for example: CREATE FOREIGN TABLE tableA(i integer ,k integer not null auto_increment primary key); CREATE FOREIGN TABLE tableB(i integer ,k integer not null auto_increment primary key) CREATE FOREIGN TABLE tableC(i integer ,k integer not null auto_increment primary key) create view v1 (i integer, k integer not null auto_increment primary key) OPTIONS (UPDATABLE true) as select x, y from tableC; create trigger on v1 instead of insert as for each row begin atomic insert into tableA (i) values (new.i); --key.k references tableA.k? insert into tableB (i) values (new.i); --key.k references tableB.k? insert into tableC (i) values(new.i); --key.k references tableC.k? was (Author: cjohn001): Hello Steven, great. But I do have one further question regarding the key variable. Does it always represent the key value of the table on which the last insert was done? I mean, in case I have multiple inserts in an insert trigger on different tables, is then the key variable always associated with the record on the table of the last insert? for example: CREATE FOREIGN TABLE tableA(integer ,k integer not null auto_increment primary key); CREATE FOREIGN TABLE tableB(integer ,k integer not null auto_increment primary key) CREATE FOREIGN TABLE tableC(integer ,k integer not null auto_increment primary key) create view v1 (i integer, k integer not null auto_increment primary key) OPTIONS (UPDATABLE true) as select x, y from tableC; create trigger on v1 instead of insert as for each row begin atomic insert into tableA (x) values (new.i); --key.k references tableA.k? insert into tableB (x) values (new.i); --key.k references tableB.k? insert into tableC (x) values(new.i); --key.k references tableC.k? > 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)

6 years, 9 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, great. But I do have one further question regarding the key variable. Does it always represent the key value of the table on which the last insert was done? I mean, in case I have multiple inserts in an insert trigger on different tables, is then the key variable always associated with the record on the table of the last insert? for example: CREATE FOREIGN TABLE tableA(integer ,k integer not null auto_increment primary key); CREATE FOREIGN TABLE tableB(integer ,k integer not null auto_increment primary key) CREATE FOREIGN TABLE tableC(integer ,k integer not null auto_increment primary key) create view v1 (i integer, k integer not null auto_increment primary key) OPTIONS (UPDATABLE true) as select x, y from tableC; create trigger on v1 instead of insert as for each row begin atomic insert into tableA (x) values (new.i); --key.k references tableA.k? insert into tableB (x) values (new.i); --key.k references tableB.k? insert into tableC (x) values(new.i); --key.k references tableC.k? > 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)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-108) Add support for swagger/openapi sources

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-108?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-108: -------------------------------------- Swagger 1 as in custom REST without an API document? > Add support for swagger/openapi sources > --------------------------------------- > > Key: TEIIDSB-108 > URL: https://issues.jboss.org/browse/TEIIDSB-108 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > There should be source support for swagger/openapi. If we don't want swagger 1 support, then this can just add support for the openapi translator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5738) Upgrade to WildFly 17

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5738?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5738. ----------------------------------- Resolution: Done Upgraded to the 17 final. Updated the docs and added a release note. > Upgrade to WildFly 17 > --------------------- > > Key: TEIID-5738 > URL: https://issues.jboss.org/browse/TEIID-5738 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Shwetha vr > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > Upgrade to the latest WildFly for the next Teiid minor release. > Note that it has not been tested if Teiid 12.2 is compatible with WildFly 16, so that could be an initial workaround. See the forum https://developer.jboss.org/thread/280075 for a discussion of managing the overlay separately from WildFly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5738) Upgrade to WildFly 17

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5738?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5738: ---------------------------------- Summary: Upgrade to WildFly 17 (was: Upgrade to WildFly 16) > Upgrade to WildFly 17 > --------------------- > > Key: TEIID-5738 > URL: https://issues.jboss.org/browse/TEIID-5738 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Shwetha vr > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > Upgrade to the latest WildFly for the next Teiid minor release. > Note that it has not been tested if Teiid 12.2 is compatible with WildFly 16, so that could be an initial workaround. See the forum https://developer.jboss.org/thread/280075 for a discussion of managing the overlay separately from WildFly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-108) Add support for swagger/openapi sources

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-108: -------------------------------------- Summary: Add support for swagger/openapi sources Key: TEIIDSB-108 URL: https://issues.jboss.org/browse/TEIIDSB-108 Project: Teiid Spring Boot Issue Type: Feature Request Reporter: Steven Hawkins Fix For: 1.3.0 There should be source support for swagger/openapi. If we don't want swagger 1 support, then this can just add support for the openapi translator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2019