[JBoss JIRA] (TEIID-147) Support for JAVA Stored Procedures
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-147?page=com.atlassian.jira.plugin.... ]
Steven Hawkins updated TEIID-147:
---------------------------------
Fix Version/s: 10.0
(was: 9.x)
We will evaluate in 10.0 if this is something that we want to pursue. We can use logic similar to the script binding that we do for objecttable to allow the procedure to declare it's language. It would then have access to well defined context objects. However with that approach queries will be executed in a synch manner as we won't be able to block/release the thread.
> Support for JAVA Stored Procedures
> ----------------------------------
>
> Key: TEIID-147
> URL: https://issues.jboss.org/browse/TEIID-147
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 9.x
> Reporter: Ramesh Reddy
> Fix For: 10.0
>
>
> Currently the Stored procedure support is lacking for both our procedure language and XQuery. Procedure support could be extended to java (or groovy) code, which will provide a powerful engine to execute a arbitrary queries.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-226) Cacheing translated commands would improve connector performance
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-226?page=com.atlassian.jira.plugin.... ]
Steven Hawkins updated TEIID-226:
---------------------------------
Fix Version/s: 10.x
(was: 9.x)
> Cacheing translated commands would improve connector performance
> ----------------------------------------------------------------
>
> Key: TEIID-226
> URL: https://issues.jboss.org/browse/TEIID-226
> Project: Teiid
> Issue Type: Feature Request
> Components: Connector API, Query Engine
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Fix For: 10.x
>
>
> Defect Tracker #16722: AD 2/17/05 - Command translation in connector - approx. half the time taken to create an Execution object is spent in command translation. If there was a way to cache the translated command, then we could eliminate that step for subsequent requests.
> Alex 2/17/05 - The problem is that the connector can be used with different vdbs, so the translation may be different even for the same query. Still seems do-able [...].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-321) Refactor symbol language objects
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-321?page=com.atlassian.jira.plugin.... ]
Steven Hawkins updated TEIID-321:
---------------------------------
Fix Version/s: 10.x
(was: 9.x)
> Refactor symbol language objects
> --------------------------------
>
> Key: TEIID-321
> URL: https://issues.jboss.org/browse/TEIID-321
> Project: Teiid
> Issue Type: Task
> Components: Query Engine
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.x
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Defect Tracker #25035: The current structuring of Symbol objects is confusing and makes planning more difficult than necessary. Changes that should be made:
> AggregateSymbol should become AggregateFunction (which should not inherit from Function) and not be a Symbol.
> SingleElementSymbol, ExpressionSymbol, and AliasSymbol should be merged to a single class DerivedSymbol
> DerivedSymbol and MultipleElementSymbol should implement SelectSymbol (as an interface rather than base class) and SelectSymbol should provide a method for getting the projected symbols.
> ElementSymbol should not directly be a DerivedSymbol.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months