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 Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5763?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5763: --------------------------------------- The first commit is in. It addresses what is described as issue 1 from the forum post - you can use the generated_key function in any procedure regardless of how the procedure is invoked. I've also added a more convenient generated_key() function that assumes just a single long value being returned. > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5765) Criteria Pushdown is not working on FULL OUTER JOIN

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5765?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5765. ----------------------------------- Fix Version/s: 12.3 12.1.2 12.2.1 Resolution: Done The check in rule push criteria after the join optimization is too broad - it was checking for any outer join. So the change was just a sanity check of a full outer join. > Criteria Pushdown is not working on FULL OUTER JOIN > --------------------------------------------------- > > Key: TEIID-5765 > URL: https://issues.jboss.org/browse/TEIID-5765 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 12.0 > Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) > Reporter: Dmitrii Pogorelov > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 12.3, 12.1.2, 12.2.1 > > > Criteria Pushdown is not working on FULL OUTER JOIN (according to query plan criteria is not pushed down at all, it's in criteria of LEFT OUTER JOIN node): > {code:noformat} > ---------------------------------------------------------------------------- > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > ProjectNode(0) output=[1] [1] > SelectNode(1) output=[a.a] a.a = 1 > JoinNode(2) [MERGE JOIN (ALREADY_SORTED/ALREADY_SORTED)] [LEFT OUTER JOIN] criteria=[a.a=b.b] output=[a.a] > AccessNode(3) output=[a.a] SELECT g_0.a AS c_0 FROM test.test_a AS g_0 ORDER BY c_0 > AccessNode(4) output=[b.b] SELECT g_0.b AS c_0 FROM dwh_my.test_a AS g_0 ORDER BY c_0 > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5765) Criteria Pushdown is not working on FULL OUTER JOIN

by Dmitrii Pogorelov (Jira)

Dmitrii Pogorelov created TEIID-5765: ---------------------------------------- Summary: Criteria Pushdown is not working on FULL OUTER JOIN Key: TEIID-5765 URL: https://issues.jboss.org/browse/TEIID-5765 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 12.0 Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) Reporter: Dmitrii Pogorelov Assignee: Steven Hawkins Criteria Pushdown is not working on FULL OUTER JOIN (according to query plan criteria is not pushed down at all, it's in criteria of LEFT OUTER JOIN node): {code:noformat} ---------------------------------------------------------------------------- OPTIMIZATION COMPLETE: PROCESSOR PLAN: ProjectNode(0) output=[1] [1] SelectNode(1) output=[a.a] a.a = 1 JoinNode(2) [MERGE JOIN (ALREADY_SORTED/ALREADY_SORTED)] [LEFT OUTER JOIN] criteria=[a.a=b.b] output=[a.a] AccessNode(3) output=[a.a] SELECT g_0.a AS c_0 FROM test.test_a AS g_0 ORDER BY c_0 AccessNode(4) output=[b.b] SELECT g_0.b AS c_0 FROM dwh_my.test_a AS g_0 ORDER BY c_0 {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5764) Refine OpenApi 3.0 Support for OData

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5764?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5764: --------------------------------------- As described in TEIIDSB-62, we need openapi.json to default to v2. And openapi.json to also accept a version query parameter. Valid values initially will be 2 and 3. > Refine OpenApi 3.0 Support for OData > ------------------------------------ > > Key: TEIID-5764 > URL: https://issues.jboss.org/browse/TEIID-5764 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3, 12.2.1 > > > Support OpenAPI 3.0 document generation with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-104: -------------------------------------- Summary: OpenApi 3.0 Support for OData Key: TEIIDSB-104 URL: https://issues.jboss.org/browse/TEIIDSB-104 Project: Teiid Spring Boot Issue Type: Feature Request Reporter: Ramesh Reddy Assignee: Ramesh Reddy 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)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5764) Refine OpenApi 3.0 Support for OData

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5764?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5764: ------------------------------------- Assignee: Steven Hawkins (was: Ramesh Reddy) > Refine OpenApi 3.0 Support for OData > ------------------------------------ > > Key: TEIID-5764 > URL: https://issues.jboss.org/browse/TEIID-5764 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3, 12.2.1 > > > Support OpenAPI 3.0 document generation with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5764) Refine OpenApi 3.0 Support for OData

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5764?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5764: ---------------------------------- Summary: Refine OpenApi 3.0 Support for OData (was: OpenApi 3.0 Support for OData) > Refine OpenApi 3.0 Support for OData > ------------------------------------ > > Key: TEIID-5764 > URL: https://issues.jboss.org/browse/TEIID-5764 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.3, 12.2.1 > > > Support OpenAPI 3.0 document generation with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5764) OpenApi 3.0 Support for OData

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5764?page=com.atlassian.jira.plugin... ] Steven Hawkins moved TEIIDSB-104 to TEIID-5764: ----------------------------------------------- Project: Teiid (was: Teiid Spring Boot) Key: TEIID-5764 (was: TEIIDSB-104) Fix Version/s: 12.3 12.2.1 (was: 1.1.0) > OpenApi 3.0 Support for OData > ----------------------------- > > Key: TEIID-5764 > URL: https://issues.jboss.org/browse/TEIID-5764 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.3, 12.2.1 > > > Support OpenAPI 3.0 document generation with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[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 commented on TEIIDSB-62: ------------------------------------- Sounds good. We should also allow /openapi.json?version=2.0.0 = v2 for good measure, then we can switch it around when 3.0 becomes mainline. No support for YML yet. > 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)

6 years, 10 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-62?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-62: --------------------------------------- To re-recap it seems that the preference is to use openapi.json defaulting to 2 and we get to choose the mechanism to select version 3. I'd vote for a query parameter over a header as that's easier to define in many client situations. /openapi.json - v2 by default /openapi.json?version=3.0.0 = v3 > 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)

6 years, 10 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