June 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5781) Deprecate the anonymous authentication mode

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5781: ------------------------------------- Summary: Deprecate the anonymous authentication mode Key: TEIID-5781 URL: https://issues.jboss.org/browse/TEIID-5781 Project: Teiid Issue Type: Quality Risk Components: Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.3 The configuration of cipher suites can be accomplished via the vm and the enabledCipherSuites property. There is no need to have a special anonymous mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-109) Allow for the usage of the spring platform transaction manager in more scenarios

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-109: -------------------------------------- Summary: Allow for the usage of the spring platform transaction manager in more scenarios Key: TEIIDSB-109 URL: https://issues.jboss.org/browse/TEIIDSB-109 Project: Teiid Spring Boot Issue Type: Enhancement Components: core Reporter: Steven Hawkins Fix For: 1.3.0 Unless an xa source is being used, we would ideally use the default platform transaction manager. This would map updates over multiple sources to best effort single phase commit. This will likely be the majority of our usage. The problem is that the platform transaction manager doesn't directly support a suspend/resume concept that is needed for our remote pg/jdbc processing logic that allows the processing thread to detach from the current work when blocked and do something else. It would be worth investigating if this functionality could be added to spring boot or if there is is some other approach that was missed with the initial investigation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5780) Support certificate based authentication into Teiid pg

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5780: ------------------------------------- Summary: Support certificate based authentication into Teiid pg Key: TEIID-5780 URL: https://issues.jboss.org/browse/TEIID-5780 Project: Teiid Issue Type: Sub-task Components: ODBC Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.3 To support the pg connection into Teiid we will do something like: - require a pg secure port using the service signing certificate: TEIIDSB-90 TEIIDSB-92 -- one clarification is that we must document how to make the pg cert dominant if both pg and jdbc secure are used TODO: - configure the pg instance to have a service signing certificate and trust the Teiid service signing certificate. If that trust seems too difficult we can just configure the connection to trust all. - configure the pg connection to Teiid to use the pg service signing certificate as the client certificate - trust the pg service signing certificate at the teiid service - we need hostname validation to be enabled and the Teiid server to map the service host name to an authenticated user (this could possibly be generalized via keycloak support to more users). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5729) Introduce mechanism or option to allow for mapping of side effect free Teiid procedures to ODATA functions, and actions if procedure has side effects

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5729?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5729. ----------------------------------- Resolution: Done The problem here is actually that the auto value for the update count is being treated the same as no updates. However to get an actual value that requires fully planning the procedure as the closest logic we have comes from the requires transaction logic on the plan. That is quite involved, so the initial fix is just to be safe and map instead to an action. The docs have been updated to say that an explicit updatecount of 0 is expected to map to a function. > Introduce mechanism or option to allow for mapping of side effect free Teiid procedures to ODATA functions, and actions if procedure has side effects > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-5729 > URL: https://issues.jboss.org/browse/TEIID-5729 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > This is a follow up regarding https://issues.jboss.org/browse/TEIID-5725 > As discussed there, Teiid currently does not map virtual procedures and functions to odata functions and procedures according to the notion of "side effect free" > Please introduce a mechanism to allow for a mapping according to adequate odata semantics. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5773) Allow for generated_key retrieval at a session level

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5773?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5773. ----------------------------------- Resolution: Done Updated the generated_key logic to use a session variable. The doc was updated as well to indicate the last value for the session is returned. > Allow for generated_key retrieval at a session level > ---------------------------------------------------- > > Key: TEIID-5773 > URL: https://issues.jboss.org/browse/TEIID-5773 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > The docs suggest that generated_key should be called in a procedure. However calling outside of a procedure will currently return no values as the keys are associated with the executing command context only. Ideally from a connection the user should be able to do: > insert into ...; > select generated_key() ...; > In separate statements and still retrieve the key value. > The workaround is to use an anonymous procedure block: > begin > insert into ...; > select generated_key() ...; > end -- 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: --------------------------------------- Great, than it seems we can move on and close the issue :) Thanks for your help! > 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: Critical > Fix For: 12.3 > > > 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: --------------------------------------- Yes, that has been addressed as well. > 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: Critical > Fix For: 12.3 > > > 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, thanks. Did you also change: >>And unintuitively for the view auto increment column to be not null: >>CREATE VIEW QuicklyAddedProducts (fkProduct long NOT NULL AUTO_INCREMENT ... In this case I would grab another snapshot. > 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: Critical > Fix For: 12.3 > > > 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-5774) Javadoc cleanup

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5774?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5774: --------------------------------------- Committed a cleanup of invalid references, param names, etc. As I recall though there was more that the plugin was complaining about. > Javadoc cleanup > --------------- > > Key: TEIID-5774 > URL: https://issues.jboss.org/browse/TEIID-5774 > Project: Teiid > Issue Type: Sub-task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > An open ended jira to cleanup the java doc to the point where the plugin can run with fail on error. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5774) Javadoc cleanup

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5774: ------------------------------------- Summary: Javadoc cleanup Key: TEIID-5774 URL: https://issues.jboss.org/browse/TEIID-5774 Project: Teiid Issue Type: Sub-task Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.3 An open ended jira to cleanup the java doc to the point where the plugin can run with fail on error. -- 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