July 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5427) Remove session/user scoped materialized views

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5427?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5427: ------------------------------------- >The other mechanism is sharing materialized views across versions of a vdb. Is that the one you are referring to? Yes, by default I would like to see the VDB scoped be global where all the VDB versions share. But I do see there is a need for this in Blue -> Green type of deployments. > Remove session/user scoped materialized views > --------------------------------------------- > > Key: TEIID-5427 > URL: https://issues.jboss.org/browse/TEIID-5427 > Project: Teiid > Issue Type: Task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > TEIID-2507 added session scoped materialized views - which are now not well aligned with any other materialization strategy. They have to be unmanaged and internal only. It would be best to completely remove the feature and recommend instead that users create global temporary tables instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5428) session scoped temp tables should get cleaned up faster

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5428: ------------------------------------- Summary: session scoped temp tables should get cleaned up faster Key: TEIID-5428 URL: https://issues.jboss.org/browse/TEIID-5428 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 11.1 Session scoped temp tables are being cleanup up via garbage collection, rather than explicitly when the session is closed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5427) Remove session/user scoped materialized views

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5427?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5427: --------------------------------------- There are two scoping features. vdb/user/session is applicable to result set cache entries. Once this feature is removed then there will be no need to specify a scope in a cache hint for a materialized view. The other mechanism is sharing materialized views across versions of a vdb. Is that the one you are referring to? > Remove session/user scoped materialized views > --------------------------------------------- > > Key: TEIID-5427 > URL: https://issues.jboss.org/browse/TEIID-5427 > Project: Teiid > Issue Type: Task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > TEIID-2507 added session scoped materialized views - which are now not well aligned with any other materialization strategy. They have to be unmanaged and internal only. It would be best to completely remove the feature and recommend instead that users create global temporary tables instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5427) Remove session/user scoped materialized views

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5427?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5427: ------------------------------------- +1, although we implemented this originally for maximum flexibility in terms of cachebility, it did not span out to be a distinct feature. Realistically, it is hard to find architecture designs that are being cached actively at the session level for individual user level, even if there are they typically for a very short duration of time. I feel Infinispan like instance caching is more suitable in situations like this. I would even go further simplification to remove the vdb scoped distinction too. Basically, we are trying to guard against the schema evolution here more than anything. > Remove session/user scoped materialized views > --------------------------------------------- > > Key: TEIID-5427 > URL: https://issues.jboss.org/browse/TEIID-5427 > Project: Teiid > Issue Type: Task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > TEIID-2507 added session scoped materialized views - which are now not well aligned with any other materialization strategy. They have to be unmanaged and internal only. It would be best to completely remove the feature and recommend instead that users create global temporary tables instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5427) Remove session/user scoped materialized views

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5427: ------------------------------------- Summary: Remove session/user scoped materialized views Key: TEIID-5427 URL: https://issues.jboss.org/browse/TEIID-5427 Project: Teiid Issue Type: Task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 11.1 TEIID-2507 added session scoped materialized views - which are now not well aligned with any other materialization strategy. They have to be unmanaged and internal only. It would be best to completely remove the feature and recommend instead that users create global temporary tables instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5426) For Each processing for instead of triggers should materialize change set before processing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5426?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5426: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1605292 Bugzilla Update: Perform > For Each processing for instead of triggers should materialize change set before processing > ------------------------------------------------------------------------------------------- > > Key: TEIID-5426 > URL: https://issues.jboss.org/browse/TEIID-5426 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 11.1, 11.0.1, 10.3.3 > > > Currently when a view is defined with Inserts, Updates and Deletes with Instead of Triggers with "FOR EACH" row processing, the change set (the rows that are changing for the statement) typically is like > {code} > loop on (select ids from (view) where predicate) > begin > procedure body > end > {code} > where there is a possibility that "procedure body" will change underlying tables such that the "loop on" query results could vary during the processing. Like concurrent updates. This could be avoided by materializing the ids in #temp table before processing any of the rows. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5426) For Each processing for instead of triggers should materialize change set before processing

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5426?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5426. ----------------------------------- Fix Version/s: 11.1 11.0.1 10.3.3 Resolution: Done Added an intermediate temp table to fully capture the change set. > For Each processing for instead of triggers should materialize change set before processing > ------------------------------------------------------------------------------------------- > > Key: TEIID-5426 > URL: https://issues.jboss.org/browse/TEIID-5426 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 11.1, 11.0.1, 10.3.3 > > > Currently when a view is defined with Inserts, Updates and Deletes with Instead of Triggers with "FOR EACH" row processing, the change set (the rows that are changing for the statement) typically is like > {code} > loop on (select ids from (view) where predicate) > begin > procedure body > end > {code} > where there is a possibility that "procedure body" will change underlying tables such that the "loop on" query results could vary during the processing. Like concurrent updates. This could be avoided by materializing the ids in #temp table before processing any of the rows. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5425) Concurrency/timing issues observed with travis builds

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5425?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5425: --------------------------------------- Can't seem to reproduce the odbc socket issue. With 10's of thousands or runs with a full cpu load it's not occurring. I'll look next to see if it's related to the vm. > Concurrency/timing issues observed with travis builds > ----------------------------------------------------- > > Key: TEIID-5425 > URL: https://issues.jboss.org/browse/TEIID-5425 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > Several unit tests have been observed to fail during travis builds occasionally: > TestODBCSocketTransport.testRegClass:757 Â» PSQL ResultSet not positioned prope... > and > TestExternalMatViews.testLazyUpdate:930 expected:<2> but was:<1> (see https://api.travis-ci.org/v3/job/405801976/log.txt) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5426) For Each processing for instead of triggers should materialize change set before processing

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-5426: ----------------------------------- Summary: For Each processing for instead of triggers should materialize change set before processing Key: TEIID-5426 URL: https://issues.jboss.org/browse/TEIID-5426 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 11.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Currently when a view is defined with Inserts, Updates and Deletes with Instead of Triggers with "FOR EACH" row processing, the change set (the rows that are changing for the statement) typically is like {code} loop on (select ids from (view) where predicate) begin procedure body end {code} where there is a possibility that "procedure body" will change underlying tables such that the "loop on" query results could vary during the processing. Like concurrent updates. This could be avoided by materializing the ids in #temp table before processing any of the rows. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5425) Concurrency/timing issues observed with travis builds

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5425: ------------------------------------- Summary: Concurrency/timing issues observed with travis builds Key: TEIID-5425 URL: https://issues.jboss.org/browse/TEIID-5425 Project: Teiid Issue Type: Bug Components: Build/Kits Reporter: Steven Hawkins Assignee: Steven Hawkins Several unit tests have been observed to fail during travis builds occasionally: TestODBCSocketTransport.testRegClass:757 Â» PSQL ResultSet not positioned prope... and TestExternalMatViews.testLazyUpdate:930 expected:<2> but was:<1> (see https://api.travis-ci.org/v3/job/405801976/log.txt) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2018