February 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2408) statistics of teiid query queuing information

by Jack Ma (JIRA)

Jack Ma created TEIID-2408: ------------------------------ Summary: statistics of teiid query queuing information Key: TEIID-2408 URL: https://issues.jboss.org/browse/TEIID-2408 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 8.2 Reporter: Jack Ma Assignee: Steven Hawkins At currently version of teiid, there is no teiid queuing information available from either teiid api or log or jmx, like how many query plans are still in the waiting queue, how many are in the active queue etc. .Thinking those queuing information is pretty critical for performance tuning up, Based on the Ramesh's suggestion, creating this request for probably a statistics max water mark in the waiting queue, and average time spent in waiting queue etc. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-196) Support creation of temp tables on physical sources.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-196?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-196: -------------------------------------- I think it's best to not address the ease of use for a teiid temporary table for the 8.3 release. The most likely usage pattern to replace an internal temporary table would look like: {code} //- create the source table source.native("CREATE [GLOBAL] TEMPORARY TABLE name IF NOT EXISTS ON COMMIT [DELETE ROWS | DROP]"); //- bring the table into Teiid CREATE FOREIGN TEMPORARY TABLE name ... //- use the table {code} For this to be correctly handled with a GLOBAL temporary table, the table name would need to be unique or the GLOBAL / table definition would need to be the same for all sessions with session specific data scoping (such as Oracle) - or the source would need to support session scoped temporary tables (such as PostgreSQL). It would also need to be accessed under a transaction so that: * the on commit behavior could ensure clean-up - as a Teiid drop is not guaranteed to occur (in some exception cases, loss of db connectivity, hard shutdown, etc.) * the source pool when using track connections by transaction will ensure that multiple uses of that source by Teiid will use the same connection/session and thus the same temporary table/data. > Support creation of temp tables on physical sources. > ---------------------------------------------------- > > Key: TEIID-196 > URL: https://issues.jboss.org/browse/TEIID-196 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ken Johnson > Assignee: Steven Hawkins > Fix For: 8.3 > > > This is a multi-part request. > First, the system should support creation of temporary tables using a physical backing store rather than buffer manger. Given multi-pass SQL's heavy use of temp tables, buffer manager can easily be overloaded with large interim results stored in temp tables. > Second, this should be a user-configurable behavior. For example, user might be able to choose a system-level or session-level default from among: > -- memory/cache > -- a source represented by a connector binding > -- a distinct temp source defined with it's own connection parameters (possibly another schema in the repository DB instance) > Ideally default selectoin should be override-able at temp table creation time through a DDL extension > In the case where multiple temp tables have been created on a source via connector, the query planner should recognize this and leverage pushdown to the temp store when later query passes access multiple temp tables. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2336) Pushdown support for arraytable

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2336?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2336: ---------------------------------- Fix Version/s: 8.4 > Pushdown support for arraytable > ------------------------------- > > Key: TEIID-2336 > URL: https://issues.jboss.org/browse/TEIID-2336 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.4 > > > Rewrite ARRAYTABLE queries as a series of cast and array_get functions calls. > This would allow translators to support efficient queries using ARRAYTABLE. > See https://community.jboss.org/thread/215915 for more information -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2407) Support temporary table on commit behavior

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2407: ------------------------------------- Summary: Support temporary table on commit behavior Key: TEIID-2407 URL: https://issues.jboss.org/browse/TEIID-2407 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4 Now that our temporary tables are transactionally aware we should support the on commit clause. Our current default for on commit is effectively "preserve rows", which is contrary to the sql specification. We should also offer delete rows and possible drop (similar to pg sql). -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2405) getVDBImports returns empty list when an importing VDB becomes active.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2405?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2405. ----------------------------------- Fix Version/s: 8.3 Resolution: Done Ensured that the entire state is cloned and that if written out the imported models will be excluded. > getVDBImports returns empty list when an importing VDB becomes active. > ---------------------------------------------------------------------- > > Key: TEIID-2405 > URL: https://issues.jboss.org/browse/TEIID-2405 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.2 > Reporter: Daniel Caros > Assignee: Steven Hawkins > Fix For: 8.3 > > > I am calling the adminapi getVDB() on a VDB that imports other VDBs. Then I am calling getVDBImports() on the VDB object that is returned. If this VDB object is in a LOADING state, it returns correct list of imported VDBs. If this VDB object is in an ACTIVE state, the call to getVDBImports() returns an empty list. We need a way to get imported VDBs when an importing VDB is ACTIVE. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2406) Quickstart to demonstrate custom database appender logger

by Van Halbert (JIRA)

Van Halbert created TEIID-2406: ---------------------------------- Summary: Quickstart to demonstrate custom database appender logger Key: TEIID-2406 URL: https://issues.jboss.org/browse/TEIID-2406 Project: Teiid Issue Type: Feature Request Components: Build/Kits Affects Versions: 8.3 Reporter: Van Halbert Assignee: Van Halbert -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2398) Web console in domain mode loose active servers and shows just inactive ones

by luca gioppo (JIRA)

[ https://issues.jboss.org/browse/TEIID-2398?page=com.atlassian.jira.plugin... ] luca gioppo commented on TEIID-2398: ------------------------------------ When you have done it can you send me the link to the new version? Is there a place like jenkins or something? I'm on 7.1.1 AS in any case so ... the strange thing is that after adding the console it states that it is a console of 7.2 ???? Maybe part of the problem? Luca > Web console in domain mode loose active servers and shows just inactive ones > ---------------------------------------------------------------------------- > > Key: TEIID-2398 > URL: https://issues.jboss.org/browse/TEIID-2398 > Project: Teiid > Issue Type: Bug > Components: Web Console > Affects Versions: 8.2 > Environment: Centos 6.3, JBoss 7.1.1 TEIID 8.2, Java 1.6 > Reporter: luca gioppo > Assignee: Ramesh Reddy > Labels: console, domain, web > Fix For: 8.3 > > Attachments: teiid.png, teiid2.png, teiid3.png, teiid4.png, teiid5.png > > > I have a domain environment (for now just one host with both the domain controllere and tow servers instances) with two server groups and one servre in each group; it will be configured to be in HA. > I added the web console to the installation (copyed the stuff in the folder and hope this was the correct way of doing) > When I go to the runtime only the stopped server are present and canno select the running one. > This makes the console un-usable since not choosing the server stop all other activity with errors. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2405) getVDBImports returns empty list when an importing VDB becomes active.

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2405?page=com.atlassian.jira.plugin... ] SBS JIRA Integration updated TEIID-2405: ---------------------------------------- Forum Reference: https://community.jboss.org/message/798934#798934 > getVDBImports returns empty list when an importing VDB becomes active. > ---------------------------------------------------------------------- > > Key: TEIID-2405 > URL: https://issues.jboss.org/browse/TEIID-2405 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.2 > Reporter: Daniel Caros > Assignee: Steven Hawkins > > I am calling the adminapi getVDB() on a VDB that imports other VDBs. Then I am calling getVDBImports() on the VDB object that is returned. If this VDB object is in a LOADING state, it returns correct list of imported VDBs. If this VDB object is in an ACTIVE state, the call to getVDBImports() returns an empty list. We need a way to get imported VDBs when an importing VDB is ACTIVE. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2405) getVDBImports returns empty list when an importing VDB becomes active.

by Daniel Caros (JIRA)

Daniel Caros created TEIID-2405: ----------------------------------- Summary: getVDBImports returns empty list when an importing VDB becomes active. Key: TEIID-2405 URL: https://issues.jboss.org/browse/TEIID-2405 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 8.2 Reporter: Daniel Caros Assignee: Steven Hawkins I am calling the adminapi getVDB() on a VDB that imports other VDBs. Then I am calling getVDBImports() on the VDB object that is returned. If this VDB object is in a LOADING state, it returns correct list of imported VDBs. If this VDB object is in an ACTIVE state, the call to getVDBImports() returns an empty list. We need a way to get imported VDBs when an importing VDB is ACTIVE. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2404) Expose buffermanager monitoring properties

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2404?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2404: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Expose buffermanager monitoring properties > ------------------------------------------ > > Key: TEIID-2404 > URL: https://issues.jboss.org/browse/TEIID-2404 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.3 > > > We should expose: > BufferServiceImpl.getUserBufferSpace - the number of megs currently used by the buffermanager disk storage. > A rough total of the memory buffer space used can be added, which would be from the BufferFrontedCacheStore concurrent bits set X block size. > Also the BufferManagerImpl could report the total estimate of objects held in memory. -- 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2013