[JBoss JIRA] Created: (TEIID-784) Enhance distinct set op processing
by Steven Hawkins (JIRA)
Enhance distinct set op processing
----------------------------------
Key: TEIID-784
URL: https://jira.jboss.org/jira/browse/TEIID-784
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.3.0
The sort operation should be able to pushed for each set op child (distinct is already eligible for pushing, but typically won't be because there's no order by). Also for union the sorted children should be fed directly into the second phase of sorting.
All of this relies on the connector guaranteeing null ordering (TEIID-715 should be repurposed to cover the language enhancement of nulls first|last)
--
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
13 years, 4 months
[JBoss JIRA] Created: (TEIID-587) Better pushdown support for exotic joins
by Steven Hawkins (JIRA)
Better pushdown support for exotic joins
----------------------------------------
Key: TEIID-587
URL: https://jira.jboss.org/jira/browse/TEIID-587
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.1.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.2.0
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 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
13 years, 4 months
[JBoss JIRA] Created: (TEIID-1214) The translators displayed in the JOPR console need a full description, not just Teiid Translator, because a 2 char. name (i.e., ws) with no description isn't clear
by Van Halbert (JIRA)
The translators displayed in the JOPR console need a full description, not just Teiid Translator, because a 2 char. name (i.e., ws) with no description isn't clear
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1214
URL: https://jira.jboss.org/browse/TEIID-1214
Project: Teiid
Issue Type: Bug
Components: Jopr Plugin
Reporter: Van Halbert
Assignee: Steve Hawkins
Priority: Minor
The translators displayed in the JOPR console need a clear description, not just Teiid Translator, because a 2 char. name (i.e., ws) with essentially no description isn't clear.
--
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