Make process plans serizializable.
----------------------------------
Key: TEIID-511
URL: https://jira.jboss.org/jira/browse/TEIID-511
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.x
Processing plans should be serializable to take advantage of replication and non-memory caches. See also TEIID-81
--
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
2 CommonTransactionTests Hang, commented out for now
----------------------------------------------------
Key: TEIID-889
URL: https://jira.jboss.org/jira/browse/TEIID-889
Project: Teiid
Issue Type: Bug
Components: Integration Tests
Affects Versions: 7.0
Reporter: Van Halbert
Assignee: Steven Hawkins
2 CommonTransactionTests hang and do not complete. Not sure why at the moment, but commenting them out for now and documenting to know to go back and investigate.
- xtestMultipleSourcePartialProcessingUsingLimit
- xtestMultipleSourcePartialProcessingUsingMakedep
--
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 commandcontext available to the evaluatablevisitor
-----------------------------------------------------------
Key: TEIID-513
URL: https://jira.jboss.org/jira/browse/TEIID-513
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.1.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.x
If the commandcontext is available to the evaluatablevisitor, then we can make a better decision about what determinism level to accept for planning function evaluation.
--
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
Enhancem multisource planning with aggregate pushdown
-----------------------------------------------------
Key: TEIID-776
URL: https://jira.jboss.org/jira/browse/TEIID-776
Project: Teiid
Issue Type: Feature Request
Affects Versions: 6.2.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.x
Multisource modification happens after all rules have been fired, which means that aggregate and other sort/distinct pushdown optimizations do not happen.
--
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 REST Support to Data Services
---------------------------------
Key: TEIID-417
URL: https://jira.jboss.org/jira/browse/TEIID-417
Project: Teiid
Issue Type: Feature Request
Components: SOAP Services
Reporter: Ted Jones
Assignee: Ted Jones
Need to add support for REST to data services. REST needs be enabled in Axis2 and a REST endpoint should be added to the data services WSDL.
--
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
Getting the Procedure Parameter metadata is not supported in ODBC
-----------------------------------------------------------------
Key: TEIID-1164
URL: https://jira.jboss.org/browse/TEIID-1164
Project: Teiid
Issue Type: Bug
Components: ODBC
Affects Versions: 7.1
Reporter: Ramesh Reddy
Currently postgreSQL uses the JDBC array types in issuing the query to read the Procedure parameters. However, Teiid does not support the Array types yet in the JDBC layer, thus this is currently not implemented. This needs to be fixed to correctly return the metadata about the procedures.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add support for connecting to Mondrian
--------------------------------------
Key: TEIID-1011
URL: https://jira.jboss.org/jira/browse/TEIID-1011
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector
Affects Versions: 7.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.1
We should add support for connecting to Mondrian (and multidimensional datasources in general) through http://www.jdbc4olap.org/.
--
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 JOPR data role display
--------------------------
Key: TEIID-1228
URL: https://jira.jboss.org/browse/TEIID-1228
Project: Teiid
Issue Type: Sub-task
Components: Jopr Plugin
Affects Versions: 7.1
Reporter: Steve Hawkins
Assignee: Steve Hawkins
Fix For: 7.1.1
Data roles should be displayed in JOPR. It would be optional to include the actual permissions. The mapped role names property should be updatable (which includes add/remove).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Derive VDB Name Using Version During Deployment in Jopr
-------------------------------------------------------
Key: TEIID-1217
URL: https://jira.jboss.org/browse/TEIID-1217
Project: Teiid
Issue Type: Feature Request
Components: Jopr Plugin
Affects Versions: 7.1
Reporter: Ted Jones
Assignee: Ted Jones
Fix For: 7.2
Need to add a configuration to the file based deployment of vdbs that contains version. From this the vdb file name should be derived. For example, if I deploy a vdb called MyVDB.vdb with a version of 3, the derived file name would be MyVDB.3.vdb.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Support Deployment of VDB via a URL in Jopr Plugin
--------------------------------------------------
Key: TEIID-1196
URL: https://jira.jboss.org/browse/TEIID-1196
Project: Teiid
Issue Type: Feature Request
Components: Jopr Plugin
Reporter: Ted Jones
Assignee: Ted Jones
Fix For: 7.1.1
Currently VDB deployment is strictly file based. Need to add support for deployment via URL. Also, when a VDB is deployed through a URL, the the "component name" supplied to the profile service deployer to save your deployment under needs to take a name and version and derive a unique name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira