February 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-833) Support tighter integration with container deployments

by Steven Hawkins (JIRA)

Support tighter integration with container deployments ------------------------------------------------------ Key: TEIID-833 URL: https://jira.jboss.org/jira/browse/TEIID-833 Project: Teiid Issue Type: Feature Request Components: Embedded, Query Engine, Server Affects Versions: 6.3.0 Reporter: Steven Hawkins Assignee: Ramesh Reddy Fix For: 6.3.0 We should be able to leverage the container: TransactionManager/XATerminator Work Management Security Connection Handling (See also TEIID-805) and have a standard deployment model for JON discovery. The initial plans are to deploy Teiid as a JCA rar and to allow for the creation of local (embedded) datasources from that instance, as well as allow for socket connections. -- 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, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-1001) Source string format for float/double/bigdecimal/timestamp can vary

by Steven Hawkins (JIRA)

Source string format for float/double/bigdecimal/timestamp can vary ------------------------------------------------------------------- Key: TEIID-1001 URL: https://jira.jboss.org/jira/browse/TEIID-1001 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 Teiid uses JDBC/Java for it's standard conversions. However the push down conversion to string of float/double/bigdecimal/timestamp can vary depending upon the actual source type and source system (db2 vs. sql server, etc.). -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-782) Add the ability to test transactions to CTC testing client

by Van Halbert (JIRA)

Add the ability to test transactions to CTC testing client ---------------------------------------------------------- Key: TEIID-782 URL: https://jira.jboss.org/jira/browse/TEIID-782 Project: Teiid Issue Type: Sub-task Reporter: Van Halbert Fix For: 6.2.0 The CTC Client needs the ability to test transactions. The idea here was to change the framework to use the transaction framework used in the jbedsp-test-integration tests. -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-998) Define a new schema based VDB deployer xml (previously defined by ConfigurationInfo.def)

by Ramesh Reddy (JIRA)

Define a new schema based VDB deployer xml (previously defined by ConfigurationInfo.def) ---------------------------------------------------------------------------------------- Key: TEIID-998 URL: https://jira.jboss.org/jira/browse/TEIID-998 Project: Teiid Issue Type: Sub-task Components: Common Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Attachments: vdb-deployer.xsd With the changes in the JCA branch the ConfigurationInfo.def file inside the VDB needs to be modified to accommodate the new connector definitions. Create a schema based XML file that can be used with both with Designer generated VDB and also for Dynamic VDB. -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-834) CTC Testing -Queries should not depend on a Stored Procedure result set if the stored procedures is not designed to return a result set.

by Warren Gibson (JIRA)

CTC Testing -Queries should not depend on a Stored Procedure result set if the stored procedures is not designed to return a result set. ---------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-834 URL: https://jira.jboss.org/jira/browse/TEIID-834 Project: Teiid Issue Type: Bug Components: Integration Tests Environment: CTC Testing Reporter: Warren Gibson Assignee: Warren Gibson Fix For: 6.2.0 In prior releases the stored procedures result sets were returned in all cases. CTC stored procedure queries were written with the expectation of a result set being returned. That is no longer the case and result sets will only be returned when the stored procedure calls for a returned result set. CTC stored procedures queries need to be reviewed to eliminate their dependencies on result sets when the procedure is not designed to return a result. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-783) Fetch enhancements

by Steven Hawkins (JIRA)

Fetch enhancements ------------------ Key: TEIID-783 URL: https://jira.jboss.org/jira/browse/TEIID-783 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 6.2.0 Allow fetchsize to be set on resultsets and do not cache batches on the client when the cursor type is forward only. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-806) JDBC connector handling of convert is inconsistent

by Steven Hawkins (JIRA)

JDBC connector handling of convert is inconsistent -------------------------------------------------- Key: TEIID-806 URL: https://jira.jboss.org/jira/browse/TEIID-806 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3.0 If a source lacks the exact representation of a Teiid type we approximate it with the closest source type. Pushed converts will typically not have the same affect as if they are evaluated in the engine. For example sources lacking byte or tinyint types are having conversions dropped rather, but the actual effect should be modulo the max byte value. We also are not ensuring that the truncation or rounding behavior is the same for all conversions - such as from a floating point number to a fixed point. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-943) Fully implement client streaming of lobs/readers/streams

by Steven Hawkins (JIRA)

Fully implement client streaming of lobs/readers/streams -------------------------------------------------------- Key: TEIID-943 URL: https://jira.jboss.org/jira/browse/TEIID-943 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1 Client transmission of large objects is either not implemented or is implemented through fully materializing. We should instead allow for streaming backed by temp files on 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

14 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-944) Provide a separate Admin connection

by Ramesh Reddy (JIRA)

Provide a separate Admin connection ----------------------------------- Key: TEIID-944 URL: https://jira.jboss.org/jira/browse/TEIID-944 Project: Teiid Issue Type: Sub-task Components: AdminApi, Server Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Currently the Admin API can be accessed from JDBC API and as well a separate connection on the same port as the JDBC connection. Since in the container environment the Admin API is based on the Profile Service this needs to be on its own connection that is subject to the same authorization checks as of the profile service/jmx-console. It will no longer available on the JDBC connection. Although, we can still serve the both connections on same port as the JDBC, by having a separate port the traffic on the Admin connection can be by default encrypted always, and the number of IO threads will be limited and do not hog the JDBC connection threads. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-851) API improvements for custom connector development

by Mark Drilling (JIRA)

API improvements for custom connector development ------------------------------------------------- Key: TEIID-851 URL: https://jira.jboss.org/jira/browse/TEIID-851 Project: Teiid Issue Type: Feature Request Components: Connector API Affects Versions: 6.1.0 Reporter: Mark Drilling Assignee: Steven Hawkins Priority: Minor I'm building a custom connector, and I was trying to figure out a way to get information on whether or not a certain column in a Source Model is a Primary or Foreign Key. Here's an example of the code I've been trying: MetadataID mdID = group.getMetadataID(); //group is an IGroup String tableName = metadata.getObject(mdID).getNameInSource(); However, there doesn't appear to be a way to determine which column is Primary or Foreign Key. One thing I did notice playing around with the API, the MetadataObject contains a TableRecordImpl object that contains all sorts of MetaData info. That class appears to have tons of great info, along with getters and setters, including one called getForeignKeyIDs. Don't know if there's maybe a reason it's abstracted such that we can't get to it, but being able to get that and the other info out of that object could be highly beneficial. Maybe this is something that could be added to the API in the future? -- 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, 6 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2010