[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, 1 month
[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, 1 month
[JBoss JIRA] (TEIID-2069) Optimze add LIMIT clause to SELECT within a Virtual Procedure using Oracle
by Johnathon Lee (JIRA)
Johnathon Lee created TEIID-2069:
------------------------------------
Summary: Optimze add LIMIT clause to SELECT within a Virtual Procedure using Oracle
Key: TEIID-2069
URL: https://issues.jboss.org/browse/TEIID-2069
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7, 7.4.1
Reporter: Johnathon Lee
Assignee: Steven Hawkins
LIMIT clause is added to Statement being optimized which fails the operation on Oracle
OPTIMIZE:
CREATE VIRTUAL PROCEDURE
BEGIN
DECLARE biginteger VARIABLES.t_pk;
VARIABLES.t_pk = (SELECT <table>.seq_gen.cpe_seq FROM <table>.seq_gen);
SELECT VARIABLES.t_pk AS result;
END
####################################################
PROCEDURE COMMAND: CREATE VIRTUAL PROCEDURE
BEGIN
DECLARE biginteger VARIABLES.t_pk;
VARIABLES.t_pk = (SELECT <table>.seq_gen.cpe_seq FROM <table>.seq_gen LIMIT 2);
SELECT VARIABLES.t_pk AS result;
END
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2234) Function pushdown issues
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2234:
-------------------------------------
Summary: Function pushdown issues
Key: TEIID-2234
URL: https://issues.jboss.org/browse/TEIID-2234
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Function validation should not prevent a function name from containing a '.' and nameinsource should be respected for ddl foreign functions.
We also have an issue with function names conflicting with system function names any time there is a check of just the descriptor name without checking the schema.
--
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, 1 month
[JBoss JIRA] (TEIID-2190) Key usage can remove predicates
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2190:
-------------------------------------
Summary: Key usage can remove predicates
Key: TEIID-2190
URL: https://issues.jboss.org/browse/TEIID-2190
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Blocker
Fix For: 8.2
The implementation strategy for predicate realignment can drop non-column equi join predicates and predicates involving the same column reused multiple times.
i.e.
create local temporary table x (e1 string, e2 integer, primary key (e1));
create local temporary table x1 (e1 string, e2 integer)
...
select x.e1 from x inner join x1 on x.e1 = x1.e1 and upper(x.e1) = x1.e2
May end up not applying the upper predicate.
--
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, 1 month
[JBoss JIRA] (TEIID-2158) Generate a Rest based service automatically based on deployed VDB
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2158:
-----------------------------------
Summary: Generate a Rest based service automatically based on deployed VDB
Key: TEIID-2158
URL: https://issues.jboss.org/browse/TEIID-2158
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.2
Currently to enable REST based services on top of the VDB, Designer provides a mechanism for user to define metadata on the procedure and gives hooks to generate Rest service based WAR file to deploy into a application server.
To support OpenShift efforts it would be good to provide this functionality out of box, when Teiid is deployed into the JBoss AS (never in embedded).
To define a scenario,
- user creates a VDB and defines one or more models
- then user creates a virtual procedure with following metadata in the options clause
REST:METHOD = GET|PUT|POST|DELETE (mandatory)
REST:URI = uri (mandatory)
REST:PRODUCES = xml|json|text (optional, if omitted will be calculated from procedures return parameter)
REST:CHARSET = character set (optional) (ex:US-ASCII, UTF-8 etc. In cases where the binary data is returned this character set will be used to convert)
where REST namesspace is defined as
SET NAMESPACE 'http://teiid.org/rest' AS REST;
- user deploys a VDB
- a jax-rs based war is created and deployed automatically at the end of vdb deployment
- if vdb is un-deployed, this jax-rs war will also be undeployed
Questions?
1) Should this enforce HTTPBasic Auth by default? since Teiid does not have a way define the DDL based metadata this is difficult.
2) Apart from above procedures, does a generic procedure that executes a add-hoc query helpful? The restriction here is the results will be in a pre-defined format not user defined.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month