September 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-597) AdminAPI method: UpdateProperties() needs to support updating the Service properties

by Van Halbert (JIRA)

AdminAPI method: UpdateProperties() needs to support updating the Service properties ------------------------------------------------------------------------------------- Key: TEIID-597 URL: https://jira.jboss.org/jira/browse/TEIID-597 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.1 Reporter: Van Halbert Assignee: Van Halbert The adminapi updateProperties(String identifier, String classname, Properties props) needs to support updating the Service properties. -- 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
6
0 / 0

[JBoss JIRA] Created: (TEIID-844) Implement metadata creation in the SalesForce connector.

by John Doyle (JIRA)

Implement metadata creation in the SalesForce connector. -------------------------------------------------------- Key: TEIID-844 URL: https://jira.jboss.org/jira/browse/TEIID-844 Project: Teiid Issue Type: Feature Request Components: Salesforce Connector Reporter: John Doyle Assignee: John Doyle Fix For: 6.3.0 The SF connector should use the new connector metadata API to produce it's own metadata. -- 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-358) Quick Start Guide / Examples needs to add derbyclient.jar to UDFs for previewing

by Paul Nittel (JIRA)

Quick Start Guide / Examples needs to add derbyclient.jar to UDFs for previewing -------------------------------------------------------------------------------- Key: TEIID-358 URL: https://jira.jboss.org/jira/browse/TEIID-358 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 6.0.0 Environment: fedora 10 Reporter: Paul Nittel Assignee: Steven Hawkins I ran into this while assisting user Bribek. When the Derby source is created and imported, a connector binding is built in the Designer. The one thing Designer does not do is place the jar file where it needs to be for previewing. The Quick Start Example needs to add the step of adding the derbyclient.jar file using the UDFs view and "Import UDF Extension Jar Files" action. IMHO, the Quick Start needs to be revisited to determine exactly what the required minimum effort is for a user to get through this. Perhaps on the Teiid side avoid all modeling and add a Quick Start on the Designer side that builds the VDB. If Teiid can do the Quick Start with just a VDB, that might be preferable. -- 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, 4 months

5
9
0 / 0

[JBoss JIRA] Created: (TEIID-673) Need to Document Alternate Means of Achieving Web Services and XML Usage Scenarios for Teiid

by Ted Jones (JIRA)

Need to Document Alternate Means of Achieving Web Services and XML Usage Scenarios for Teiid -------------------------------------------------------------------------------------------- Key: TEIID-673 URL: https://jira.jboss.org/jira/browse/TEIID-673 Project: Teiid Issue Type: Task Reporter: Ted Jones Assignee: Ted Jones For 6.2, we need to provide an alternative means to handle the current Web Services and XML Usage Scenarios for Teiid. These scenarios are captured as sub tasks of this task. Here is a link to the meeting notes regarding this subject: https://docspace.corp.redhat.com/clearspace/docs/DOC-21488 -- 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, 4 months

3
4
0 / 0

[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

15 years, 4 months

4
4
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

15 years, 4 months

3
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

15 years, 4 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

15 years, 4 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

15 years, 4 months

2
4
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

15 years, 4 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2009