[JBoss JIRA] Created: (TEIID-1371) Translator does not unload correctly
by Ramesh Reddy (JIRA)
Translator does not unload correctly
------------------------------------
Key: TEIID-1371
URL: https://jira.jboss.org/browse/TEIID-1371
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.2
Reporter: Ramesh Reddy
Priority: Minor
When a Translator is deployed while Server is running, it loads dynamically, however if you replace with a new version, it says it unloaded the old, and loads the new, however it continues to use the old classes from previous version of the Translator. This was confusing, and time consuming for me to develop a Translator and keep re-starting the Server.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] Created: (TEIID-1560) Add support for user defined / pushdown aggregate functions
by Steven Hawkins (JIRA)
Add support for user defined / pushdown aggregate functions
-----------------------------------------------------------
Key: TEIID-1560
URL: https://issues.jboss.org/browse/TEIID-1560
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.0
Add support for user defined aggregate functions. This would also affect the function model metadata. Our aggregate handling logic will need to be generalized to make this possible. Starting with the parser we've got special handling for built-in aggregates.
for user defined aggregate handling just a static method will not work as the function needs to retain state across each group. Could require that the implementing class extends AggregateFunction.
Could also allow user defined aggregates to take an order by clause.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[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
12 years, 5 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
12 years, 6 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
12 years, 6 months