July 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2067) Global temporary tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2067?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2067: --------------------------------------- Added the initial implementation. Still need to work on change detection with caching, how designer should should create them, and better plan caching/creation (although that is a general issue with our temp logic). > Global temporary tables > ----------------------- > > Key: TEIID-2067 > URL: https://issues.jboss.org/browse/TEIID-2067 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7 > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.5 > > > Currently, temp tables are scoped to the teiid session (eg, jdbc connection) that created them. I would like temp tables visible to all sessions. It is acceptable and even desirable that temp tables use an external database a la external materialization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2589) Subplans are repeated in the reported query plan

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2589?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2589. ----------------------------------- Resolution: Done Corrected the double looping. > Subplans are repeated in the reported query plan > ------------------------------------------------ > > Key: TEIID-2589 > URL: https://issues.jboss.org/browse/TEIID-2589 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > TEIID-2256 introduced a regression where by subplans are added to the plan descriptions too many times. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2591) Incorrect values returned from system table on dependent side of join

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2591?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2591. ----------------------------------- Resolution: Done Moved the projection correction to be a general check. > Incorrect values returned from system table on dependent side of join > --------------------------------------------------------------------- > > Key: TEIID-2591 > URL: https://issues.jboss.org/browse/TEIID-2591 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5 > > > If a system table is marked as the dependent side of a join (should be rarely planned, but can be forced with a makedep) the system table access is not corrected for the projection and may return values that are not matched to the columns requested. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2067) Global temporary tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2067?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2067: ---------------------------------- Fix Version/s: 8.5 Component/s: Query Engine Moving into 8.5 to support Oracle/ANSI style global temporary tables. Via DDL (but not at runtime) you can use from any schema: create global temporary table ... and the session specific temporary table will be created at access time. This will effectively provide support for passing results into virtual procedures using a well-defined table. Internally this leverages the session table store and the metadata record will be marked as a virtual temporary table (as opposed to a physical temporary table, which maps to a foreign table brought in temporarily). To support this from Designer would require additional metadata. > Global temporary tables > ----------------------- > > Key: TEIID-2067 > URL: https://issues.jboss.org/browse/TEIID-2067 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7 > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.5 > > > Currently, temp tables are scoped to the teiid session (eg, jdbc connection) that created them. I would like temp tables visible to all sessions. It is acceptable and even desirable that temp tables use an external database a la external materialization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2591) Incorrect values returned from system table on dependent side of join

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2591: ------------------------------------- Summary: Incorrect values returned from system table on dependent side of join Key: TEIID-2591 URL: https://issues.jboss.org/browse/TEIID-2591 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.4.1, 8.5 If a system table is marked as the dependent side of a join (should be rarely planned, but can be forced with a makedep) the system table access is not corrected for the projection and may return values that are not matched to the columns requested. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2590) Use both the general and specific hint in the oracle hint

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2590: ------------------------------------- Summary: Use both the general and specific hint in the oracle hint Key: TEIID-2590 URL: https://issues.jboss.org/browse/TEIID-2590 Project: Teiid Issue Type: Enhancement Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4.1, 8.5 The documentation behavior is to use the specific OR general hint (preferring the specific). The request is to use both. Will likely implement as a behavioral change without the need to specify a translator property to enable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2589) Subplans are repeated in the reported query plan

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2589: ------------------------------------- Summary: Subplans are repeated in the reported query plan Key: TEIID-2589 URL: https://issues.jboss.org/browse/TEIID-2589 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.2 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4.1, 8.5 TEIID-2256 introduced a regression where by subplans are added to the plan descriptions too many times. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2588) create temp table with not null column toString not correct

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2588?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2588. ----------------------------------- Resolution: Done corrected the toString > create temp table with not null column toString not correct > ----------------------------------------------------------- > > Key: TEIID-2588 > URL: https://issues.jboss.org/browse/TEIID-2588 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > There is no space between the column type and the not null constraint. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2588) create temp table with not null column toString not correct

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2588: ------------------------------------- Summary: create temp table with not null column toString not correct Key: TEIID-2588 URL: https://issues.jboss.org/browse/TEIID-2588 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4.1, 8.5 There is no space between the column type and the not null constraint. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- Continuing the discussion from the TEIID-2578, where I got still struck is Teiid has two different implementations for materialization internal and external, which are totally different. What I was thinking is we need to bring these two scenarios under same management of loading, refreshing, updating etc. In this scenario the only difference would be, if the user opted for external materialization, the call would be delegated to translator that is supporting the source table, for internal materialization have known internal translator which backed by something similar to current global temp table logic. To support creation of table(s) in this case, I thought I would need to first add the metadata addition facilities from TEIID-2578. But, I see I could amend the metadata at VDB deploy time to fit the needs internal materialization with out need for TEIID-2578. For this I would opt as you suggested to use extension metadata over Hibernate code generation, as that would not satisfy the requirements. I think we still need to leave the "creation of table" task to the user, we could either log the schema details (DDL) for materialization tables at deploy time, or leave it upto the tooling to provide hook to gather those up from extension metadata. That leaves with creation of "Status" table, we could select one of materialization targets for this and generate schema. To begin with, I do not need to modify any internal matview stuff, just barrow the logic from it, when complete, do the switch over with internal translator. I think this is close to what you are saying, may be not including the internal mat view stuff. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 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 2013