August 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5448) Infinispan: Nested table delete not working

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-5448: ----------------------------------- Summary: Infinispan: Nested table delete not working Key: TEIID-5448 URL: https://issues.jboss.org/browse/TEIID-5448 Project: Teiid Issue Type: Bug Components: Infinispan Affects Versions: 10.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 11.1 The nested table entries when criteria associated with parent table does not work. For ex: {code} delete from PhoneNumber where number = '3333' and Person_id = 1 {code} Where Person_id needs to come from parent table -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5445) Atomic block is ignored when working with execute immediate command

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5445?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5445. ----------------------------------- Fix Version/s: 11.1 10.3.4 11.0.2 Resolution: Done Updated the logic to still start a txn when a dynamic sql instruction is used. > Atomic block is ignored when working with execute immediate command > ------------------------------------------------------------------- > > Key: TEIID-5445 > URL: https://issues.jboss.org/browse/TEIID-5445 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 10.2 > Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Fix For: 11.1, 10.3.4, 11.0.2 > > > When calling in atomic block a proc which is throwing an exception after updating some rows these changed rows won't be rolled back. That is running the following query: > {code:sql} > begin atomic > call test_upd.upd(); > end ;; > {code} > all changes done in the test_upd.upd virtual procedure won't be rolled back in case of a thrown exception there. If I'm not mistaken such behavior was introduced in scope of TEIID-4504 issue (after introducing the Program.instructionsRequireTransaction method). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5447) support for percent_rank, cume_dist, nth_value

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5447?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5447: ---------------------------------- Description: Implementations for percent_rank, cume_dist, nth_value will have similar logic to ntile TEIID-5442 so they will be simple to add as well. (was: As a SQL developer, I like to be able to issue queries using NTILE functions such as {{SELECT id, zip5, ntile(100) OVER(ORDER BY geopgraphy) as percentile FROM svi2105_us_zip5.svi2015_us_zip5;}}) Reporter: Steven Hawkins (was: Norbert Funke) > support for percent_rank, cume_dist, nth_value > ---------------------------------------------- > > Key: TEIID-5447 > URL: https://issues.jboss.org/browse/TEIID-5447 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > Implementations for percent_rank, cume_dist, nth_value will have similar logic to ntile TEIID-5442 so they will be simple to add as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5447) support for percent_rank, cume_dist, nth_value

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5447: ------------------------------------- Summary: support for percent_rank, cume_dist, nth_value Key: TEIID-5447 URL: https://issues.jboss.org/browse/TEIID-5447 Project: Teiid Issue Type: Feature Request Components: Common Reporter: Norbert Funke Assignee: Steven Hawkins As a SQL developer, I like to be able to issue queries using NTILE functions such as {{SELECT id, zip5, ntile(100) OVER(ORDER BY geopgraphy) as percentile FROM svi2105_us_zip5.svi2015_us_zip5;}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5447) support for percent_rank, cume_dist, nth_value

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5447?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5447: ---------------------------------- Component/s: Query Engine (was: Common) > support for percent_rank, cume_dist, nth_value > ---------------------------------------------- > > Key: TEIID-5447 > URL: https://issues.jboss.org/browse/TEIID-5447 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Norbert Funke > Assignee: Steven Hawkins > > As a SQL developer, I like to be able to issue queries using NTILE functions such as > {{SELECT id, zip5, > ntile(100) OVER(ORDER BY geopgraphy) as percentile > FROM svi2105_us_zip5.svi2015_us_zip5;}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5445) Atomic block is ignored when working with execute immediate command

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5445?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5445: --------------------------------------- > Wasn't sure if that was an error or expected behaviour. If it's an appropriate exception that seems ok - you'd expect an exception as well if you tried to explicitly start a local transaction. > Atomic block is ignored when working with execute immediate command > ------------------------------------------------------------------- > > Key: TEIID-5445 > URL: https://issues.jboss.org/browse/TEIID-5445 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 10.2 > Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > > When calling in atomic block a proc which is throwing an exception after updating some rows these changed rows won't be rolled back. That is running the following query: > {code:sql} > begin atomic > call test_upd.upd(); > end ;; > {code} > all changes done in the test_upd.upd virtual procedure won't be rolled back in case of a thrown exception there. If I'm not mistaken such behavior was introduced in scope of TEIID-4504 issue (after introducing the Program.instructionsRequireTransaction method). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5445) Atomic block is ignored when working with execute immediate command

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5445?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5445: ---------------------------------- Priority: Major (was: Blocker) TEIID-4509 introduced this change building on TEIID-4076 and TEIID-4504. The logic assumed that the update model count property would be set if a transaction were required. That is the documented default behavior of execute immediate - http://teiid.github.io/teiid-documents/master/content/reference/Procedure... However I agree that in this case it leads to an odd outcome of not starting the explicitly declared transaction, so an adjustment is needed. The workaround is to add an update clause to the execute immediate command. > Atomic block is ignored when working with execute immediate command > ------------------------------------------------------------------- > > Key: TEIID-5445 > URL: https://issues.jboss.org/browse/TEIID-5445 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 10.2 > Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > > When calling in atomic block a proc which is throwing an exception after updating some rows these changed rows won't be rolled back. That is running the following query: > {code:sql} > begin atomic > call test_upd.upd(); > end ;; > {code} > all changes done in the test_upd.upd virtual procedure won't be rolled back in case of a thrown exception there. If I'm not mistaken such behavior was introduced in scope of TEIID-4504 issue (after introducing the Program.instructionsRequireTransaction method). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5445) Atomic block is ignored when working with execute immediate command

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5445?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5445: ------------------------------------- Unrelated comment to this issue, however, I have seen atomic blocks stop the execution with exception when no transaction manager is present and transactions are disabled. Wasn't sure if that was an error or expected behaviour. > Atomic block is ignored when working with execute immediate command > ------------------------------------------------------------------- > > Key: TEIID-5445 > URL: https://issues.jboss.org/browse/TEIID-5445 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 10.2 > Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > > When calling in atomic block a proc which is throwing an exception after updating some rows these changed rows won't be rolled back. That is running the following query: > {code:sql} > begin atomic > call test_upd.upd(); > end ;; > {code} > all changes done in the test_upd.upd virtual procedure won't be rolled back in case of a thrown exception there. If I'm not mistaken such behavior was introduced in scope of TEIID-4504 issue (after introducing the Program.instructionsRequireTransaction method). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5013) Google Spreadsheet Data Sources with custom client_id and client_secret

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5013?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5013: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1618343 Bugzilla Update: Perform > Google Spreadsheet Data Sources with custom client_id and client_secret > ----------------------------------------------------------------------- > > Key: TEIID-5013 > URL: https://issues.jboss.org/browse/TEIID-5013 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.x > Environment: JDV6.3 / Teiid 8.12 / Teiid Desinger 10.0.1 > Reporter: Hiroki Daicho > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.3 > > > When getting an OAuth Refresh Token, it needs to use a fixed client_id and client_secret such as > "217138521084.apps.googleusercontent.com" and "gXQ6-lOkEjE1lVcz7giB4Poy". > Currently, no way to change another client_id/client_secret. > It had better to be able to use the client_id/client_secret from each google account. > - Teiid 8.13 : Getting an OAuth Refresh Token > https://docs.jboss.org/author/display/teiid813final/Google+Spreadsheet+Da... > - Teiid 9.3 : Getting an OAuth Refresh Token > https://teiid.gitbooks.io/documents/content/v/9.3.x/admin/Google_Spreadsh... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5445) Atomic block is ignored when working with execute immediate command

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5445?page=com.atlassian.jira.plugin... ] Work on TEIID-5445 started by Steven Hawkins. --------------------------------------------- > Atomic block is ignored when working with execute immediate command > ------------------------------------------------------------------- > > Key: TEIID-5445 > URL: https://issues.jboss.org/browse/TEIID-5445 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 10.2 > Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > > When calling in atomic block a proc which is throwing an exception after updating some rows these changed rows won't be rolled back. That is running the following query: > {code:sql} > begin atomic > call test_upd.upd(); > end ;; > {code} > all changes done in the test_upd.upd virtual procedure won't be rolled back in case of a thrown exception there. If I'm not mistaken such behavior was introduced in scope of TEIID-4504 issue (after introducing the Program.instructionsRequireTransaction method). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 5 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 August 2018