August 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-360) SQLServer SQLTranslator issues

by Steven Hawkins (JIRA)

SQLServer SQLTranslator issues ------------------------------ Key: TEIID-360 URL: https://jira.jboss.org/jira/browse/TEIID-360 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 The time literal for Access/SQLServer is incorrect - should use 1970 not 1900 Limit for a set op needs to use a subquery Support for repeat should be aliased to replicate -- 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

14 years, 9 months

1
7
0 / 0

[JBoss JIRA] Created: (TEIID-455) Config edits should use optimistic locking

by Steven Hawkins (JIRA)

Config edits should use optimistic locking ------------------------------------------ Key: TEIID-455 URL: https://jira.jboss.org/jira/browse/TEIID-455 Project: Teiid Issue Type: Bug Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.x Config edits are atomic, but do not enforce consistency - the last one always wins. Optimistic locking should be used to properly ensure consistency. Also versions should be restorable. Currently it's not expected that multiple admins will be making changes concurrently, so this is not a critical issue. -- 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

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-801) PropertyUtils.resolveNestedProperties has side effect of adding all "default" properties to the list while resolving

by Ramesh Reddy (JIRA)

PropertyUtils.resolveNestedProperties has side effect of adding all "default" properties to the list while resolving -------------------------------------------------------------------------------------------------------------------- Key: TEIID-801 URL: https://jira.jboss.org/jira/browse/TEIID-801 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.2.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 While PropertyUtils.resolveNestedProperties resolves the nested properties, if the property object passed in has "default" properties set then it will read though all of them adds to the main property object, thus "default" properties lose their status as default. -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-805) Enable JDBC Connector to provide a way to obtain connection through JNDI

by Ramesh Reddy (JIRA)

Enable JDBC Connector to provide a way to obtain connection through JNDI ------------------------------------------------------------------------ Key: TEIID-805 URL: https://jira.jboss.org/jira/browse/TEIID-805 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 6.2.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 When Teiid is deployed in "embedded" profile under JBoss AS or Glassfish etc, it would be nice if the Data Source information can be obtained from container to used with Connector Binding for VDB. This will some times eliminates the providing the connection information in duplication, and also keeps the developers with configuring what they already know. This is going to experimental feature, as we think there may be some connection pooling, thread context issues with transactions etc. The prosed way to configure this will be providing the following property in the Connector Binding properties <Connector Name="Books Connector" ComponentType="Oracle Connector"> <Properties> <Property Name="ConnectionSource">JNDI:Books</Property> <Property Name="DeployedName">Books Connector</Property> </Properties> </Connector> Traditionally "ConnectionSource" is used to define a class name that is responsible to make the connection like Driver, Data Source class names, here the definition will be expanded to accommodate JNDI look up when the value of this property starts with "JNDI:" If there are better alternative solutions please comment. -- 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

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-509) Add new logging level so that server startup information can be logged and be differentiated from critical/warning level entries

by Van Halbert (JIRA)

Add new logging level so that server startup information can be logged and be differentiated from critical/warning level entries -------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-509 URL: https://jira.jboss.org/jira/browse/TEIID-509 Project: Teiid Issue Type: Feature Request Components: Server Reporter: Van Halbert Assignee: Steven Hawkins Currently, at server startup, nothing is being written to the hostcontroller or vmprocess logs. The previous server started information is no longer being written because of the log level wasn't being differentiated from actual critical/warning messages. Therefore, a new level should be created so that the minimal server startup information can continue to be written to the logs. -- 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

15 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-381) Migrate Teiid JOPR Plugin from Product to Project

by Ted Jones (JIRA)

Migrate Teiid JOPR Plugin from Product to Project -------------------------------------------------- Key: TEIID-381 URL: https://jira.jboss.org/jira/browse/TEIID-381 Project: Teiid Issue Type: Task Components: Build/Kits Reporter: Ted Jones Assignee: Ted Jones Fix For: 6.0.0 The Teiid JOPR Plugin source currently resides on the project side. It needs to be moved to project and incorporated into the TEIID build process. -- 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

15 years, 3 months

4
10
0 / 0

[JBoss JIRA] Created: (TEIID-685) Define Metadata aware Connector API

by Ramesh Reddy (JIRA)

Define Metadata aware Connector API ----------------------------------- Key: TEIID-685 URL: https://jira.jboss.org/jira/browse/TEIID-685 Project: Teiid Issue Type: Sub-task Components: Connector API Reporter: Ramesh Reddy Assignee: Steven Hawkins Priority: Critical Fix For: 6.2.0 Connector API needs to be extended, such that a connector can selectively implement an interface with which it can expose the metadata of the connector. This is similar to the concept of JDBC drivers exposing the metadata of the sources they are connected to. At a minimum, this API must expose all the available - Tables, with corresponding elements - Procedures with corresponding parameters in the data source. There should also be a way to define user defined properties on all the objects, that can used by tools as they fit. Please comment, if there are any specific features you would like this to extend, as PK, FK, Unique keys, indexes etc. Overtime, it is expectation that this will be grown to full blown metadata store API as the teiid-metadata project. -- 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

15 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-665) Add "authorization" service

by Ramesh Reddy (JIRA)

Add "authorization" service --------------------------- Key: TEIID-665 URL: https://jira.jboss.org/jira/browse/TEIID-665 Project: Teiid Issue Type: Sub-task Components: AdminApi, Embedded, Query Engine, Server Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.2.0 Add authorization service to "embedded". This service will provide functionality "embedded" to check if a given user is entitled to follow though a given administrative task or has a required role to carry on a operation a virtual data base. -- 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

15 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIID-677) Document/test a Means of Exposing a Teiid Source as a REST Service

by Ted Jones (JIRA)

Document/test a Means of Exposing a Teiid Source as a REST Service ------------------------------------------------------------------- Key: TEIID-677 URL: https://jira.jboss.org/jira/browse/TEIID-677 Project: Teiid Issue Type: Sub-task Components: Documentation Affects Versions: 6.1.0 Reporter: Ted Jones Assignee: Ted Jones Fix For: 6.2.0 -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-771) Simplify lob handling in the buffermanager

by Steven Hawkins (JIRA)

Simplify lob handling in the buffermanager ------------------------------------------ Key: TEIID-771 URL: https://jira.jboss.org/jira/browse/TEIID-771 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 Lob handling in the buffermanager relies upon overloading the notion of tuple source group and on reassigning the streamable obejcts to the latest tuple source / group. However it's possible for the same streamable object to be associated with multiple tuple sources. Callers should not be forced to handle invalidreferenceexceptions, since implementors of udf, or even internal code, will fail without explicit handling. -- 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

15 years, 3 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2009