[JBoss JIRA] (TEIID-3360) Provide an option to virtualize source exceptions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3360?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3360:
----------------------------------
Fix Version/s: 9.1
(was: 9.0)
> Provide an option to virtualize source exceptions
> -------------------------------------------------
>
> Key: TEIID-3360
> URL: https://issues.jboss.org/browse/TEIID-3360
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> Currently we'll pass the source exception along with the Teiid exception. And from source sql exceptions we'll also rely the sql state/code. When connecting to databases of different types it would be best to return a common set of codes.
> There is exception mapping logic in Hibernate that we could reuse, but this could apply to the non-jdbc sources such that a predictable code will seen by Teiid clients.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 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: 9.x
(was: 9.0)
> 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: 9.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
(v6.4.11#64026)
9 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: 9.x
(was: 9.0)
> 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: 9.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
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TEIID-587) Better pushdown support for exotic joins
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-587?page=com.atlassian.jira.plugin.... ]
Steven Hawkins updated TEIID-587:
---------------------------------
Fix Version/s: 9.x
(was: 9.0)
> Better pushdown support for exotic joins
> ----------------------------------------
>
> Key: TEIID-587
> URL: https://issues.jboss.org/browse/TEIID-587
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.1.0
> Reporter: Steven Hawkins
> Fix For: 9.x
>
>
> Our optimizations get in the way of Salesforce pushdown. Specifically rewriting like when possible to = and converting outer joins to inner joins. In both cases we would need to not perform the optimization in the first place or convert into an acceptable form prior to pushdown.
> The next is that salesforce, while requiring key criteria also allows other criteria in the left outer join on clause (which would be the same as having criteria on the nested relationship query in the salesforce query). With the capabilities as currently defined this would cause the query to not be pushed down. We should consider adding a relational supported join criteria type that requires key criteria but allows for outside criteria. Also we should treat the lack of inner join support to mean that criteria on the inner side of an outer join cannot be pushed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months