[JBoss JIRA] Created: (TEIID-1328) API request: Programatically modify the VDB
by Mark Addleman (JIRA)
API request: Programatically modify the VDB
--------------------------------------------
Key: TEIID-1328
URL: https://jira.jboss.org/browse/TEIID-1328
Project: Teiid
Issue Type: Feature Request
Components: AdminApi
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Priority: Minor
I'd like an API to programatically modify the VDB. It would be ideal to modify the VDB using DDL through Teiid. Our primary use case is accessing a dynamic set of datasources through Teiid. When a datasource is added, we would INSERT the appropriate entries into MODEL, PROPERTIES, DATASOURCES tables. Teiid would reread the appropriate metadata from the associated translators.
--
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
13 years, 4 months
[JBoss JIRA] Created: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner
by Mark Addleman (JIRA)
API request: rewrite query/command before it reaches the teiid planner
-----------------------------------------------------------------------
Key: TEIID-1326
URL: https://jira.jboss.org/browse/TEIID-1326
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
I'd like an API to inspect and rewrite a user query/command before it reaches the Teiid planner. The use case is to rewrite the query/command to implement view-like capabilities. For example:
SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as:
SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t
I imagine this API would be similar to the translator API: it would receive a data structure representing the query/command and use a visitor to rewrite the query. As a convenience, it would be nice to have something similar to the SQLConversionVisitor.
--
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
13 years, 5 months
[JBoss JIRA] Created: (TEIID-1604) Rationalize the context objects
by Steven Hawkins (JIRA)
Rationalize the context objects
-------------------------------
Key: TEIID-1604
URL: https://issues.jboss.org/browse/TEIID-1604
Project: Teiid
Issue Type: Quality Risk
Components: Connector API, Query Engine
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.0
The the CommandContext and the ExecutionContext should have their methods rationalized so that there is a uniform way to access information (ExecutionContext.getCommandContext().getSession().getUsername() vs. ExecutionContext.getUserName()) and/or at least ensure that method names are the same.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (TEIID-1680) issues with correlation and aggregation
by Steven Hawkins (JIRA)
issues with correlation and aggregation
---------------------------------------
Key: TEIID-1680
URL: https://issues.jboss.org/browse/TEIID-1680
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
subqueries used in the having/select clause of a query with grouping only understand correlated element symbols - not correlated grouping expressions or correlated aggregate values.
If a nested aggregate contains only outer references, then it should be treated as a correlated value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months