Document/test Alternative Means to Acheive Current XML Document Scenarios
-------------------------------------------------------------------------
Key: TEIID-678
URL: https://jira.jboss.org/jira/browse/TEIID-678
Project: Teiid
Issue Type: Sub-task
Components: Documentation
Affects Versions: 6.1.0
Reporter: Ted Jones
Assignee: Steven Hawkins
Fix For: 6.2.0
1. Start with an XML Schema to build a Document that can be filled with relational, heterogeneous data and "shipped around"
2. Given an XML document/message definition, submit a query on the document with criteria defined within the document structure
3. Send an input document, produce and output document
--
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
Document/test a Means of Bottom-up Web Services in Teiid
--------------------------------------------------------
Key: TEIID-675
URL: https://jira.jboss.org/jira/browse/TEIID-675
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
Document/test a Means of Top-down WSDL Consumption
--------------------------------------------------
Key: TEIID-674
URL: https://jira.jboss.org/jira/browse/TEIID-674
Project: Teiid
Issue Type: Sub-task
Components: Documentation
Affects Versions: 6.1.0
Reporter: Ted Jones
Assignee: Steven Hawkins
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
JDBC Connector deregistration logic is incorrect.
-------------------------------------------------
Key: TEIID-713
URL: https://jira.jboss.org/jira/browse/TEIID-713
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.2.0
The current deregistration logic is checking the wrong classloader. It should be using the context class loader to compare against the driver's classloader.
--
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
Translate criteria validation issues
------------------------------------
Key: TEIID-720
URL: https://jira.jboss.org/jira/browse/TEIID-720
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.2.0
Translate criteria should not accept criteria containing an OR, since the logic assumes that it can always use predicates independently (or worse the current logic would turn an OR into an AND). Also the validation check needs to check each user predicate and not exit early if a particular criteria type is not being translated.
--
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
Distinct aggregate type mismatch bug
------------------------------------
Key: TEIID-726
URL: https://jira.jboss.org/jira/browse/TEIID-726
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.2.0
A query such as "SELECT AVG(DISTINCT ByteNum) FROM BQT1.HugeA" that has different input (byte) and output (double) types will fail due to bad initialization logic on the aggregate function.
--
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
getProcedures procedureName pattern logic correct
-------------------------------------------------
Key: TEIID-714
URL: https://jira.jboss.org/jira/browse/TEIID-714
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
The DatabaseMetaData getProcedures call is checking the procedureName against the short name, not the full name.
--
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
Lookup function does not implicitly convert search argument
-----------------------------------------------------------
Key: TEIID-727
URL: https://jira.jboss.org/jira/browse/TEIID-727
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.1.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.2.0
The lookup function search argument should be of the same type as the key element, otherwise seemingly valid lookups will return no results i.e. lookup('foo', 'bar', 'integercolumn', <short value>)
--
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 JDBC 4 style DatabaseMetaData getColumns
------------------------------------------------
Key: TEIID-724
URL: https://jira.jboss.org/jira/browse/TEIID-724
Project: Teiid
Issue Type: Feature Request
Components: JDBC Driver
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
The getColumns call should return the additional columns
SCOPE_CATALOG
SCOPE_SCHEMA
SCOPE_TABLE
SOURCE_DATA_TYPE
IS_AUTOINCREMENT
This is currently useful so that the autoincrement value can be obtained.
--
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
Deleted connector bindings remain in the system state
-----------------------------------------------------
Key: TEIID-610
URL: https://jira.jboss.org/jira/browse/TEIID-610
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.1.1
If a connector binding is first stopped and then removed, it remains in the system state (but is otherwise removed from the system).
--
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