[JBoss JIRA] (TEIID-2182) Mechanism to hook up event listener into Teiid runtime
by Anil Allewar (JIRA)
Anil Allewar created TEIID-2182:
-----------------------------------
Summary: Mechanism to hook up event listener into Teiid runtime
Key: TEIID-2182
URL: https://issues.jboss.org/browse/TEIID-2182
Project: Teiid
Issue Type: Feature Request
Components: AdminApi, Server
Affects Versions: 8.1
Environment: Windows 7 64 bit
Reporter: Anil Allewar
Assignee: Steven Hawkins
It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization.
This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application.
Please see the thread below for the context & details
https://community.jboss.org/message/756060
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (TEIID-2253) Multi-source isssues
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2253:
-------------------------------------
Summary: Multi-source isssues
Key: TEIID-2253
URL: https://issues.jboss.org/browse/TEIID-2253
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
The design of the multi-source feature has several issues that need addressed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (TEIID-2254) Avoid name conflicts with source_name column
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2254:
-------------------------------------
Summary: Avoid name conflicts with source_name column
Key: TEIID-2254
URL: https://issues.jboss.org/browse/TEIID-2254
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Allow the multi-source column name to be configurable, or something more teiid specific, or use extension metadata, etc. to avoid name conflicts with source columns named source_name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (TEIID-669) Support "pass though" SQL commands to sources
by Ramesh Reddy (JIRA)
Support "pass though" SQL commands to sources
---------------------------------------------
Key: TEIID-669
URL: https://jira.jboss.org/jira/browse/TEIID-669
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Fix For: 6.2.0
Currently there is no mechanism in Teiid, when a query is submitted to a runtime engine that is passed through the query engine unadulterated and unmodified and submitted directly to a source connector. All queries are parsed, optimized, re-written. Some times this limits the functionality in Teiid, when a user would like to execute a query that is very "source" specific. For example Oracle supports lots of Oracle specific functions that are not supported by the SQL spec, to support execution of these in Teiid user need to resort to UDF, which is cumbersome and involves modelling.
Another benefit of this is also to pass DDL to sources, currently since Teiid does not support DDL, this is not possible at all.
There is no-expectation that these queries are part of any data integration, these are one off queries that enhance user experience with Teiid if they use this feature. Command Payload mechanism is similar system that is used for authentication and authorization needs at the connector level, this feature can use similar techniques or use some custom extension to the language to define a query 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
12 years
[JBoss JIRA] (TEIID-2255) Allow for non-literal source_name values
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2255:
-------------------------------------
Summary: Allow for non-literal source_name values
Key: TEIID-2255
URL: https://issues.jboss.org/browse/TEIID-2255
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
The current design of multi-source requires that the source_name is a literal, which prevents more common usage patterns, such as a prepared statement.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years