September 2009 - teiid-issues - Jboss List Archives

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-196?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-196: --------------------------------- Fix Version/s: 7.0 (was: 6.3.0) > Support creation of temp tables on physical sources. > ---------------------------------------------------- > > Key: TEIID-196 > URL: https://jira.jboss.org/jira/browse/TEIID-196 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ken Johnson > Fix For: 7.0 > > > 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-679) Make all scripts use TEIID_HOME

by Ramesh Reddy (JIRA)

Make all scripts use TEIID_HOME ------------------------------- Key: TEIID-679 URL: https://jira.jboss.org/jira/browse/TEIID-679 Project: Teiid Issue Type: Sub-task Reporter: Ramesh Reddy Fix For: 6.2.0 Define TEIID_HOME environment variable to be used in all the scripts that start, stop and manage the server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-712) JDBC Metadata SQLXML type is wrong

by Steven Hawkins (JIRA)

JDBC Metadata SQLXML type is wrong ---------------------------------- Key: TEIID-712 URL: https://jira.jboss.org/jira/browse/TEIID-712 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 JDBC Metadata should report the sql type for SQLXML as 2009 not 2000 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-689) Improve numeric transforms

by Steven Hawkins (JIRA)

Improve numeric transforms -------------------------- Key: TEIID-689 URL: https://jira.jboss.org/jira/browse/TEIID-689 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 The numeric transforms should use valueof methods as much as possible to reuse pooled instances. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-711) Add Google Analytics support to the Teiid.org site.

by Ramesh Reddy (JIRA)

Add Google Analytics support to the Teiid.org site. --------------------------------------------------- Key: TEIID-711 URL: https://jira.jboss.org/jira/browse/TEIID-711 Project: Teiid Issue Type: Task Components: Documentation Reporter: Ramesh Reddy Fix For: 6.2.0 It appears you need to insert a .js blurb into the pages you want to track. Figure out what needs to be done, add to magnolia pages and send out email about how this can viewed to the teiid-user and teiid-dev lists. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-718) Translate criteria fails on prepared statement update/delete criteria

by Steven Hawkins (JIRA)

Translate criteria fails on prepared statement update/delete criteria --------------------------------------------------------------------- Key: TEIID-718 URL: https://jira.jboss.org/jira/browse/TEIID-718 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.2.0 Translate criteria pulls values/references from the parent command that cannot be evaluated in the context of the update procedure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-729) Default keystore may lead to confusion or provide false sense of security in encrypting passwords

by Ramesh Reddy (JIRA)

Default keystore may lead to confusion or provide false sense of security in encrypting passwords ------------------------------------------------------------------------------------------------- Key: TEIID-729 URL: https://jira.jboss.org/jira/browse/TEIID-729 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Currently Teiid source code contains a default "teiid.keystore", which is then used by any component (connector binding) in encrypting password. Designer does use this to encrypt the password as it does not have it's own private keystore. This poses 1) False sense of security, as this is mere obfuscation as "keystore" available to anybody. 2) If the Designer provides a keystore of its own, now it becomes the burden on the user to share this same keystore on the runtime environment to enable decrypting the password. Currently this major issue in connector binding as not starting, or somebody imports previous configuration where the passwords are encrypted with different keystore. The simple solution is not provide a "default" keystore. If Designer does not provide a private keystore, then passwords in plain text in the connector binding properties. That will seamlessly run in Teiid runtime, if user does not care about having clear text passwords. That may be situation in DEV environments. In production environments during runtime (if required) Teiid will provide tools and instructions as to how to encrypt passwords. If the user does provide keystore in the Designer then it is user responsibility to share this keystore with runtime environment, that they work in sync in encrypting and decrypting the password. Users will be provided with scripts to generate a keystore with Teiid kit, with which they can use to encrypt the passwords. So, this will make the encryption as an option rather than requirement in the Teiid system. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-681) Fix logger for JBoss cache, JBossTM integration to use the same log file as the rest of the system

by Ramesh Reddy (JIRA)

Fix logger for JBoss cache, JBossTM integration to use the same log file as the rest of the system -------------------------------------------------------------------------------------------------- Key: TEIID-681 URL: https://jira.jboss.org/jira/browse/TEIID-681 Project: Teiid Issue Type: Sub-task Components: Common Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Teiid was using its own logging framework before and JBoss Cache and JBoss Transactions integration code was never were written to use the Teiid's native logger. They were written such that they were redirected to apache commons logging --> log4j. Now that Teiid uses the Log4J, all these subsystems need to redirect their logs to main teiid logger which will redirect to the log4j. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-719) Authorization Realms are being checked in case dependent way

by Ramesh Reddy (JIRA)

Authorization Realms are being checked in case dependent way ------------------------------------------------------------ Key: TEIID-719 URL: https://jira.jboss.org/jira/browse/TEIID-719 Project: Teiid Issue Type: Bug Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 When enforcing the data role entitlements on VDB the realm is computed as = Vdb-Name + Version and checked against the VDB that user is connected to. If the user connected to VDB with a different case (as connection is case in-independent of the VDB name) than what the VDB is defined as, then the user is never entitled against data which he/she should be. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
3
0 / 0

[JBoss JIRA] Closed: (TEIID-722) Determining the Teiid runtime instace identity could be error prone

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-722?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-722. -------------------------------- > Determining the Teiid runtime instace identity could be error prone > ------------------------------------------------------------------- > > Key: TEIID-722 > URL: https://jira.jboss.org/jira/browse/TEIID-722 > Project: Teiid > Issue Type: Bug > Components: Embedded, Server > Affects Versions: 6.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.2.0 > > > The current way instance id generated for the uniquely identifying the runtime engine could be wrong. Now that "processname" is available in the property, that name should be used as the identifier instead of int identifier now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 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 September 2009