June 2019 - teiid-issues - Jboss List Archives

[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, I am sorry, but I do not have enough Java background to be able to build and remotely debug the sources in an Eclipse environment. I hope the following will help you https://c.gmx.net/@328076122686231878/aW-zSH_GTzaajkuYGZPtbQ In the TeiidMySQL package you can find a docker-compose file with a mysql db and a teiid server with yesterdays git sources. In the dockerfile you can also see the mysql driver configuration. I tested with both variants XA and non-XA. The mysql container will be initialized with three tables which are from the simplified example in our previous discussions. The teiid container will be initialized with the relevant vdb for these tables. I also attached a curl script which sends a POST request to show the error. And finally I also added the Teiid Web Console to the container to show you the issue with missing runtime information. The second bug we discussed this week. > 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-5066) Move resource-adapters configuration style more adaptable to Spring/OpenShift based datasources

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5066?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5066: ---------------------------------- Fix Version/s: (was: 12.x) > Move resource-adapters configuration style more adaptable to Spring/OpenShift based datasources > ----------------------------------------------------------------------------------------------- > > Key: TEIID-5066 > URL: https://issues.jboss.org/browse/TEIID-5066 > Project: Teiid > Issue Type: Enhancement > Components: Connector API > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > The current configuration in the resource-adapters, i.e. ManagedConnectionFactory and managed connection are so tightly integrated with JCA semantics that use of this connection code else where in environments like Spring Boot or Embedded or OpenShift makes it either cumbersome or impossible. > All resource-adapter modules need to be refactored such that JCA semantics are add-ons rather than main part of it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2869) Support consuming REST based service that is secured by SAML

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-2869?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2869: ---------------------------------- Fix Version/s: (was: 12.x) > Support consuming REST based service that is secured by SAML > ------------------------------------------------------------ > > Key: TEIID-2869 > URL: https://issues.jboss.org/browse/TEIID-2869 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > Add SSO based support for consuming the REST based web-services. Currently only HTTP-Basic is supported. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4523) CXF is not used by Salesforce BulkConnection

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4523?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4523: ---------------------------------- Fix Version/s: (was: 12.x) > CXF is not used by Salesforce BulkConnection > -------------------------------------------- > > Key: TEIID-4523 > URL: https://issues.jboss.org/browse/TEIID-4523 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > > TEIID-3493 added the CXF transport, but it's not used by the salesforce BulkConnection. In v22 they make use of a static call, so we won't make a change there. With 34 we can extend the SalesforceConnectorConfig createConnection - but a HttpURLConnection is expected so this may not be straight-forward. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5543) Configuration Option for default OData format

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5543?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5543: ---------------------------------- Fix Version/s: (was: 12.x) > Configuration Option for default OData format > ---------------------------------------------- > > Key: TEIID-5543 > URL: https://issues.jboss.org/browse/TEIID-5543 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Optional > > It would be great to have a config option to set the default format for odata responses which is chosen if no Accept header was set to request the format. > SapUI5 / OpenUI5 for example sends Accept * / * > Would be great if the admin could decide on the default format in such cases. > See related discussion https://developer.jboss.org/thread/279113 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5741) Upgrade to Thorntail 2.4

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5741?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5741. ----------------------------------- Resolution: Done Released a Teiid Thorntail 2.1.0 aligned to Teiid 12.2.1 and Thorntail 2.4 - this will be the terminal release. > Upgrade to Thorntail 2.4 > ------------------------ > > Key: TEIID-5741 > URL: https://issues.jboss.org/browse/TEIID-5741 > Project: Teiid > Issue Type: Feature Request > Components: thorntail > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: tt-2.1.0 > > > As a likely terminal release, we should provide Java 11 support via Thorntail 2.4. > Since 2.4 is based upon WildFly 15.0.1, this will likely be off of 12.2.x, rather than 12.3.x. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5757) Remove the need for the odata role

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5757?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5757. ----------------------------------- Resolution: Done Opted to leave the security role in the web app, but to automatically grant the odata role. The admin may modify the teiid-security security domain to remove the odata role grant. > Remove the need for the odata role > ---------------------------------- > > Key: TEIID-5757 > URL: https://issues.jboss.org/browse/TEIID-5757 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > Similar to TEIIDSB-85 the rationale for having an odata role no longer seems valid. It will simplify usage if that is no longer required. -- 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: --------------------------------------- No, there is no trace logging currently related to this. Can you attache to this issue a reproducer vdb and mysql table? > 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] (TEIIDSB-106) Provide ability to dynamically provide the URL query parameters for Rest Calls

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-106?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-106: --------------------------------- Component/s: JPA > Provide ability to dynamically provide the URL query parameters for Rest Calls > ------------------------------------------------------------------------------ > > Key: TEIIDSB-106 > URL: https://issues.jboss.org/browse/TEIIDSB-106 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: JPA > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > When using the rest based called on @RestConfiguration, headers can be sent as user specific values, however, there is no facility for the URL parameters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-105) Modelling a Json entitty with array of "details"

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-105?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-105: --------------------------------- Component/s: JPA > Modelling a Json entitty with array of "details" > ------------------------------------------------ > > Key: TEIIDSB-105 > URL: https://issues.jboss.org/browse/TEIIDSB-105 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: JPA > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > When using the @JsonTable the construct only supports reading the array type of same data types, with mixed type it does not work. For ex: > {code} > [1, 1, 3] > {code} > works, but > {code} > [1, "two", 3.0] > {code} > does not work. If the user chooses to read it as a string array converting the values to match Teiid semantics it is not possible. However, when it is created as > {code} > { id: 1, desc: "two", weight: 3.0} > {code} > can be read an entity. The array form could also be modeled as an entity with single parameter as `string[]` -- 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