Add support for a set statement
-------------------------------
Key: TEIID-906
URL: https://jira.jboss.org/jira/browse/TEIID-906
Project: Teiid
Issue Type: Feature Request
Components: JDBC Driver
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.0
We should add support in the JDBC driver to set execution properties via a set statement. This makes it unnecessary to us the custom MMStatement api in most circumstances.
--
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
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
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
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
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
Make the Connector (type) and RAR name be the same
--------------------------------------------------
Key: TEIID-1051
URL: https://jira.jboss.org/jira/browse/TEIID-1051
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 7.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.0
Currently in the Admin API in 7.0 M3
getConnectorNames() call returns the Connectors that are available in the system. These are the Teiid Connector RAR files. However, ".RAR" extension is truncated for this call. When the a Connection Factory is created, it contains the "rar-name" as the full name with the extension. They both need to be same.
--
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
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
PostgreSQL pushdown query SELECT COUNT(*) FROM BQT1.SmallA - producing NullPointerException
---------------------------------------------------------------------------------------------
Key: TEIID-1014
URL: https://jira.jboss.org/jira/browse/TEIID-1014
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Reporter: Warren Gibson
Assignee: Steven Hawkins
Attachments: JavaNullPointer.txt
SELECT COUNT(*) FROM xxxxxxxxxx is producing Java Null Pointer Exceptions in PostgreSQL pushdown. Log attached.
Examples:
SELECT COUNT(*) FROM BQT1.SmallA
SELECT COUNT(*) FROM BQT1.MediumA
SELECT COUNT(*) FROM BQT1.LargeA
SELECT COUNT(*) FROM BQT2.SmallB
SELECT COUNT(*) FROM BQT2.MediumB
--
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
Provide deployer for the Translation Layer components.
------------------------------------------------------
Key: TEIID-1079
URL: https://jira.jboss.org/jira/browse/TEIID-1079
Project: Teiid
Issue Type: Sub-task
Components: Server
Affects Versions: 7.0
Environment: 7.0 M3
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.0
The translation layer properties will be provided to the teiid engine through "-tl.xml" properties. Teiid must provide a deployer to read this properties and create appropriate translation layer.
--
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
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