July 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-143) Query should 'find' connector types and jars rather than have them predefined in the config.

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-143: ------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Architecture changes are too great with runtime environment and designer integration for 6.2 moving to 6.3 > Query should 'find' connector types and jars rather than have them predefined in the config. > -------------------------------------------------------------------------------------------- > > Key: TEIID-143 > URL: https://jira.jboss.org/jira/browse/TEIID-143 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: John Doyle > Fix For: 6.3.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Currently, dqp as delived with Designer is preconfigured with connector types. I think it should discover the connectors that are available upon startup. This would make it easier to add connectors to a kit. The current process for adding a connector to a kit is manual and error prone. We have problems with it on nearly every release. > This is also an attractive feature for embedding query in other environments. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-254) Metadata query for procedure columns needs work

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-254?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-254: --------------------------------- Issue Type: Quality Risk (was: Task) Fix Version/s: 6.3.0 (was: 6.2.0) Priority: Minor (was: Major) Moving to 6.3, since this is only an issue for those with large numbers of procedures in their vdb. > Metadata query for procedure columns needs work > ----------------------------------------------- > > Key: TEIID-254 > URL: https://jira.jboss.org/jira/browse/TEIID-254 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.3.0 > > > Defect Tracker #24885: Even if procedure name criteria is supplied for the QUERY_PROCEDURE_COLUMNS, it is applied to a synthetic column - which can only be processed after all rows are retrieved. It looks like there may be other procedure name values in the system tables that would be a better place for this criteria (or at least more join criteria could be added under the ProcedureParams query) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-254) Metadata query for procedure columns needs work

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-254?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIID-254: -------------------------------------- The simplest fix would be to change the System.ProcedureParams query from SELECT DISTINCT p.ModelName, PROC_NAME AS ProcedureName, pp.NAME AS Name, RUNTIME_TYPE_NAME AS DataType, POSITION, lookup('SystemPhysical.PROC_PARAM_TYPE_ENUM', 'NAME', 'CODE', DIRECTION) AS Type, is_optional AS Optional, PRECISION, LENGTH AS TypeLength, SCALE, RADIX, lookup('SystemPhysical.NULL_TYPE_ENUM', 'NAME', 'CODE', NULL_TYPE) AS NullType FROM (SELECT SystemPhysical.PROC_PARAMS.PROC_NAME, SystemPhysical.PROC_PARAMS.NAME, SystemPhysical.PROC_PARAMS.RUNTIME_TYPE_NAME, SystemPhysical.PROC_PARAMS.POSITION, convert(SystemPhysical.PROC_PARAMS.DIRECTION, integer) AS DIRECTION, SystemPhysical.PROC_PARAMS.IS_OPTIONAL, SystemPhysical.PROC_PARAMS.PRECISION, SystemPhysical.PROC_PARAMS.LENGTH, SystemPhysical.PROC_PARAMS.SCALE, SystemPhysical.PROC_PARAMS.RADIX, SystemPhysical.PROC_PARAMS.NULL_TYPE, SystemPhysical.PROC_PARAMS.PROC_UUID FROM SystemPhysical.PROC_PARAMS UNION ALL SELECT rs.PROC_NAME, c.NAME, c.RUNTIME_TYPE_NAME, c.POSITION, 4, {b'false'}, c.PRECISION, c.LENGTH, c.SCALE, c.RADIX, c.NULL_TYPE, rs.PROC_UUID FROM SystemPhysical.PROC_RESULT_SETS AS rs, SystemPhysical.COLUMNS AS c WHERE rs.UUID = c.PARENT_UUID) AS pp, System.Procedures AS p WHERE PROC_UUID = p.UID to SELECT DISTINCT p.ModelName, p.FullName AS ProcedureName, pp.NAME AS Name, RUNTIME_TYPE_NAME AS DataType, POSITION, lookup('SystemPhysical.PROC_PARAM_TYPE_ENUM', 'NAME', 'CODE', DIRECTION) AS Type, is_optional AS Optional, PRECISION, LENGTH AS TypeLength, SCALE, RADIX, lookup('SystemPhysical.NULL_TYPE_ENUM', 'NAME', 'CODE', NULL_TYPE) AS NullType FROM (SELECT SystemPhysical.PROC_PARAMS.NAME, SystemPhysical.PROC_PARAMS.RUNTIME_TYPE_NAME, SystemPhysical.PROC_PARAMS.POSITION, convert(SystemPhysical.PROC_PARAMS.DIRECTION, integer) AS DIRECTION, SystemPhysical.PROC_PARAMS.IS_OPTIONAL, SystemPhysical.PROC_PARAMS.PRECISION, SystemPhysical.PROC_PARAMS.LENGTH, SystemPhysical.PROC_PARAMS.SCALE, SystemPhysical.PROC_PARAMS.RADIX, SystemPhysical.PROC_PARAMS.NULL_TYPE, SystemPhysical.PROC_PARAMS.PROC_UUID FROM SystemPhysical.PROC_PARAMS UNION ALL SELECT c.NAME, c.RUNTIME_TYPE_NAME, c.POSITION, 4, {b'false'}, c.PRECISION, c.LENGTH, c.SCALE, c.RADIX, c.NULL_TYPE, rs.PROC_UUID FROM SystemPhysical.PROC_RESULT_SETS AS rs, SystemPhysical.COLUMNS AS c WHERE rs.UUID = c.PARENT_UUID) AS pp, System.Procedures AS p WHERE PROC_UUID = p.UID so that the the searchable p.FullName is used as the ProcedureName. > Metadata query for procedure columns needs work > ----------------------------------------------- > > Key: TEIID-254 > URL: https://jira.jboss.org/jira/browse/TEIID-254 > Project: Teiid > Issue Type: Task > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 6.2.0 > > > Defect Tracker #24885: Even if procedure name criteria is supplied for the QUERY_PROCEDURE_COLUMNS, it is applied to a synthetic column - which can only be processed after all rows are retrieved. It looks like there may be other procedure name values in the system tables that would be a better place for this criteria (or at least more join criteria could be added under the ProcedureParams query) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-259) Create Teiid Server Kit

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-259?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-259: ------------------------------------ The build scripts are modified such that current "embedded" kit can be used in multi purpose, either in either "embedded" mode or in standalone server mode. The way user enables the environment defines how the run time is started. 1) If the specifies the embedded specific URL, the runtime is loaded into host JVM, and user has Teiid Embedded 2) If server is manually started, and user uses the Server specific, the client program can connect to Teiid Server instance over the socket. Startup scripts for running the server are provided in the "bin" folder. There may additional scripts coming to this folder depending upon the user feed back. All the configuration is defined in the "deploy.properties". Currently there are no documentation on how this woks, however by the time 6.2 is released they will be provided. One notable difference from legacy Server is the SOAP related web services, will not be supported in new Teiid runtime environment, these capabilities are provided through additional JBoss tools. Look at TEIID-673 > Create Teiid Server Kit > ----------------------- > > Key: TEIID-259 > URL: https://jira.jboss.org/jira/browse/TEIID-259 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 6.2.0 > > > Build a server kit and corresponding configuration installer for 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-192) Add the ability to switch the identity on connections

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-192?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-192: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Moving security enhancements from clients to the 6.3 release. They are not critical for 6.3 and are not for typical use cases. > Add the ability to switch the identity on connections > ----------------------------------------------------- > > Key: TEIID-192 > URL: https://jira.jboss.org/jira/browse/TEIID-192 > Project: Teiid > Issue Type: Feature Request > Components: Common, JDBC Driver > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.3.0 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Based upon oracle and sql server abilities, we should offer methods to assert and newly authenticate an identity on an existing connection. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-218) Security URL properties handling

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-218?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-218: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Moving security enhancements from clients to the 6.3 release. They are not critical for 6.3 and are not for typical use cases. > Security URL properties handling > -------------------------------- > > Key: TEIID-218 > URL: https://jira.jboss.org/jira/browse/TEIID-218 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver, Server > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.3.0 > > > Defect Tracker #24196: Security URL properties are currently a mess in that there are three properties, clientToken, credentials, and trustedPayload that are all eventually treated at the trustedPayload. This is not desirable. Instead we should pass all of the connection properties to the membership service (as a map) for access by membership domains. This would remove the need to specifically pass the trustedPayload and application name as parameters. This could also be done for connectors provided that the message or the transport containing the connection properties is encrypted. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-249) Need well-known multi-payload container

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-249?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-249: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Moving security enhancements from clients to the 6.3 release. They are not critical for 6.3 and are not for typical use cases. > Need well-known multi-payload container > --------------------------------------- > > Key: TEIID-249 > URL: https://jira.jboss.org/jira/browse/TEIID-249 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Driver, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 6.3.0 > > > Defect Tracker #21547: Currently it's up to users to build some container and extend connectors if they want to pass multiple payloads through the system. Would probably be better if we provided such a container, JDBC connectors were aware of it, and our commandPayload() functions worked with it. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-514) ORDER BY should have ability to include columns not specified in the SELECT clause

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-514?page=com.atlassian.jira.plug... ] Steven Hawkins reassigned TEIID-514: ------------------------------------ Assignee: Steven Hawkins > ORDER BY should have ability to include columns not specified in the SELECT clause > ---------------------------------------------------------------------------------- > > Key: TEIID-514 > URL: https://jira.jboss.org/jira/browse/TEIID-514 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > > Client request to allow an ORDER BY clause to include columns other than those specified in the SELECT clause, as in the following query: > SELECT col1, col2, col3 > FROM tableA > ORDER BY col4 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-207) Forward and Backward Compatibility of MetaMatrix JDBC Driver

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-207?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-207: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Pushing to 6.3. There have been no changes to the client/jdbc classes that would break between 6.1 and 6.2. Also there's been no community push as of yet to provide backwards compatibility with MetaMatrix 5.x. AdminApi related functionality has changed to accommodate the new server mode. > Forward and Backward Compatibility of MetaMatrix JDBC Driver > ------------------------------------------------------------ > > Key: TEIID-207 > URL: https://jira.jboss.org/jira/browse/TEIID-207 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: 6.3.0 > > > The MetaMatrix JDBC driver should be forward and backward compatible with newer/older versions of Enterprise Server. It is understood that certain protocol changes may break the compatibility but this should only happen in major releases and not affect Service Packs and maintenance releases. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-186) Expose catalog information and props in Connector API metadata [PEC]

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-186?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-186: --------------------------------- Fix Version/s: 6.3.0 (was: 7.x) > Expose catalog information and props in Connector API metadata [PEC] > -------------------------------------------------------------------- > > Key: TEIID-186 > URL: https://jira.jboss.org/jira/browse/TEIID-186 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.3.0 > > > Defect Tracker #20304: This request is to expose information on catalogs and schemas in relational models as separate entities and also to expose extension properties on those entities. Currently, only models and groups exist in runtime indexes and Connector API metadata and catalogs and schemas are just treated as namespace elements for groups. The XML Connector uses those catalogs and would like to store extension properties on them and retrieve those in the connector. -- 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, 9 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 July 2009