[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
[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
[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
[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
[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