February 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2139) Factor out common table expressions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2139?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2139: ---------------------------------- Fix Version/s: 8.4 (was: 8.3) pushing to 8.4 > Factor out common table expressions > ----------------------------------- > > Key: TEIID-2139 > URL: https://issues.jboss.org/browse/TEIID-2139 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.4 > > > Query planner should factor out common table expressions within queries so they are only executed once. See https://community.jboss.org/message/742355 for more context. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2334) Add keys to system tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2334?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2334: --------------------------------------- Corrected an issue with the property table metadata for CR1. > Add keys to system tables > ------------------------- > > Key: TEIID-2334 > URL: https://issues.jboss.org/browse/TEIID-2334 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.3 > > > The metadata changes to implement indexing on the system tables means that it is quite appropriate to include primary keys / indexes on system tables. We should also probably add unique constraints to uids. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2388) Add Used Buffer Disk Space Metric to RHQ Plugin

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2388?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2388: ------------------------------------- {code} /subsystem=teiid:engine-statistics {code} Will get you the stats about Teiid > Add Used Buffer Disk Space Metric to RHQ Plugin > ----------------------------------------------- > > Key: TEIID-2388 > URL: https://issues.jboss.org/browse/TEIID-2388 > Project: Teiid > Issue Type: Feature Request > Components: RHQ > Affects Versions: 8.3 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.3 > > > Need to add Used Buffer Space metric to the 8.x Teiid RHQ Plugin -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2293) Update Object-Translator to add support for JPA/Hibernate search annotations in the metadata processor

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2293?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2293: -------------------------------- Fix Version/s: (was: 8.3) > Update Object-Translator to add support for JPA/Hibernate search annotations in the metadata processor > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-2293 > URL: https://issues.jboss.org/browse/TEIID-2293 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.2 > Reporter: Van Halbert > > Update Object-Translator to add support for JPA/Hibernate search annotations in the metadata processor. Coordinate with the JPA/OGM work that is being done. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2411) Add schema name to metadata validation messages

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2411?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2411. --------------------------------- Labels: CR1 (was: ) Resolution: Done Took SteveH suggestion and replaced all the occurrences with getFullName on all the meatadata validation log messages. > Add schema name to metadata validation messages > ----------------------------------------------- > > Key: TEIID-2411 > URL: https://issues.jboss.org/browse/TEIID-2411 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.2 > Reporter: Paul Lysak > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.3 > > > Currently metadata validation messages don't contain schema name, so when working with lot of schemas it may be difficult to find out problematic element. For example, if table SOME_TABLE has no columns then > org.teiid.query.metadata.MetadataValidator.MinimalMetadata.execute() will log following error message: > TEIID31071 Invalid table; Table SOME_TABLE has no columns defined > And there's no ability to detect later to which schema problematic table belongs. > I suggest to append schema name - either by simple concatenation in MetadataValidator.java: > metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31071, scmena.getName()+"."+t.getName())); > or by changing message bundle i18n.properties: > TEIID31071=Invalid table; Table {0}.{1} has no columns defined > and providing message parameters in MetadataValidator.java: > metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31071, scmena.getName(), t.getName())); > There are also another validation messages in MetadataValidator.java which could be improved in similar way. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2409) To add execution id into data src command_log

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2409?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2409. --------------------------------- Labels: CR1 (was: ) Resolution: Done Added the executionID to the COMMAND_LOG message for the DATA source calls > To add execution id into data src command_log > --------------------------------------------- > > Key: TEIID-2409 > URL: https://issues.jboss.org/browse/TEIID-2409 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Ramesh Reddy > Priority: Trivial > Labels: CR1 > Fix For: 8.3 > > > When we try to analyze the command_log, for some user query, it push multiple data source queries to same data source, in this case, both request id and source command id are same, so it is impossible to pair those data source queries from the command_log (please see discussion: https://community.jboss.org/message/799183#799183). Adding the execution id into the data source command_log should make following combination key unique (request id + source command id + execution id) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2409) To add execution id into data src command_log

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2409?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2409: -------------------------------- Issue Type: Enhancement (was: Feature Request) Assignee: Ramesh Reddy (was: Steven Hawkins) Fix Version/s: 8.3 Priority: Trivial (was: Major) Complexity: Low I am going to append the executionID to the sourceCommandID to fix the issue. > To add execution id into data src command_log > --------------------------------------------- > > Key: TEIID-2409 > URL: https://issues.jboss.org/browse/TEIID-2409 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Ramesh Reddy > Priority: Trivial > Fix For: 8.3 > > > When we try to analyze the command_log, for some user query, it push multiple data source queries to same data source, in this case, both request id and source command id are same, so it is impossible to pair those data source queries from the command_log (please see discussion: https://community.jboss.org/message/799183#799183). Adding the execution id into the data source command_log should make following combination key unique (request id + source command id + execution id) -- 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, 2 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 resolved TEIID-196. ---------------------------------- Resolution: Done Updated the reference guide for the permissions and syntax to create a foreign temporary table. The initial implementation does not have any pushdown side-effects (there is no source action on create/drop). Any ease of use features as an internal temporary table replacement can be addressed later. > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2411) Add schema name to metadata validation messages

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2411?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2411: -------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) Fix Version/s: 8.3 Complexity: Low > Add schema name to metadata validation messages > ----------------------------------------------- > > Key: TEIID-2411 > URL: https://issues.jboss.org/browse/TEIID-2411 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.2 > Reporter: Paul Lysak > Assignee: Ramesh Reddy > Fix For: 8.3 > > > Currently metadata validation messages don't contain schema name, so when working with lot of schemas it may be difficult to find out problematic element. For example, if table SOME_TABLE has no columns then > org.teiid.query.metadata.MetadataValidator.MinimalMetadata.execute() will log following error message: > TEIID31071 Invalid table; Table SOME_TABLE has no columns defined > And there's no ability to detect later to which schema problematic table belongs. > I suggest to append schema name - either by simple concatenation in MetadataValidator.java: > metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31071, scmena.getName()+"."+t.getName())); > or by changing message bundle i18n.properties: > TEIID31071=Invalid table; Table {0}.{1} has no columns defined > and providing message parameters in MetadataValidator.java: > metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31071, scmena.getName(), t.getName())); > There are also another validation messages in MetadataValidator.java which could be improved in similar way. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2411) Add schema name to metadata validation messages

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2411?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2411: --------------------------------------- Actually those calls should just be using the getFullName method (which does include the schema) instead of getName. > Add schema name to metadata validation messages > ----------------------------------------------- > > Key: TEIID-2411 > URL: https://issues.jboss.org/browse/TEIID-2411 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.2 > Reporter: Paul Lysak > Assignee: Steven Hawkins > > Currently metadata validation messages don't contain schema name, so when working with lot of schemas it may be difficult to find out problematic element. For example, if table SOME_TABLE has no columns then > org.teiid.query.metadata.MetadataValidator.MinimalMetadata.execute() will log following error message: > TEIID31071 Invalid table; Table SOME_TABLE has no columns defined > And there's no ability to detect later to which schema problematic table belongs. > I suggest to append schema name - either by simple concatenation in MetadataValidator.java: > metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31071, scmena.getName()+"."+t.getName())); > or by changing message bundle i18n.properties: > TEIID31071=Invalid table; Table {0}.{1} has no columns defined > and providing message parameters in MetadataValidator.java: > metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31071, scmena.getName(), t.getName())); > There are also another validation messages in MetadataValidator.java which could be improved in similar way. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2013