[ https://jira.jboss.org/jira/browse/TEIID-175?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-175:
---------------------------------
Fix Version/s: 6.1.0
(was: 6.2.0)
> Asynchronous union results
> --------------------------
>
> Key: TEIID-175
> URL: https://jira.jboss.org/jira/browse/TEIID-175
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.0.0
> Reporter: Marc Shirley
> Priority: Optional
> Fix For: 6.1.0
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> This is really a request for a dup-removal algorithm that can return results without waiting for all results. This would be generally less efficient than the full-sort approach, so it would be good to base the decision on a hint or costing information.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-178?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-178:
---------------------------------
Fix Version/s: 6.1.0
(was: 6.2.0)
> Implement sort minimization in process plans
> --------------------------------------------
>
> Key: TEIID-178
> URL: https://jira.jboss.org/jira/browse/TEIID-178
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.x
> Reporter: Steven Hawkins
> Priority: Optional
> Fix For: 6.1.0
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Sorting for order bys, dub removal, merge joins, and grouping should be minimized after the process plan has been determined.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-183?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-183:
---------------------------------
Fix Version/s: 6.2.0
(was: 7.x)
This is now much easier to do with the dependentcriteriaprocessor. ruleplanprocedures could be expanded to include associating non-pushdown criteria with access nodes and mark it as dependent.
> user "or" and "in" criteria should generate multiple queries in some situations
> -------------------------------------------------------------------------------
>
> Key: TEIID-183
> URL: https://jira.jboss.org/jira/browse/TEIID-183
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.x
> Reporter: Steven Hawkins
> Fix For: 6.2.0
>
>
> Defect Tracker #23857: Since web services and relational wrappers around procedures do not support "in" or "or" criteria, an enhancement would be union the results of multipe queries rather than not pushing down the criteria or not validating the query entirely.
--
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
Schema Imports in Auot-discovered WSDL Missing Application Context
------------------------------------------------------------------
Key: TEIID-530
URL: https://jira.jboss.org/jira/browse/TEIID-530
Project: Teiid
Issue Type: Bug
Components: SOAP Services
Affects Versions: 6.0.0
Reporter: Ted Jones
Assignee: Ted Jones
Fix For: 6.1.0
The URL for imported schemas in the auto-discovered WSDL is missing the application context. The dynamic WSDL schema urls are being created correctly.
--
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
Capabilites are not checked appropriately for join criteria
-----------------------------------------------------------
Key: TEIID-534
URL: https://jira.jboss.org/jira/browse/TEIID-534
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.1.0
Only function support is currently checked for criteria push down. Unsupported predicates, etc. will pass through.
--
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
Add support for pushdown of select clause and join clause subqueries
--------------------------------------------------------------------
Key: TEIID-535
URL: https://jira.jboss.org/jira/browse/TEIID-535
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.1.0
Currently we only allow pushdown of subqueries in the where clause.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-82?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-82.
---------------------------------
Resolution: Done
Addressed with the creation of a SubqueryAwareEvaluator that performs in place evaluation of subqueries following roughly the same rules as the subqueryprocessorutility. One drawback is that the initial processing plan needs cloned, however preregistration of the plan with the evaluator could eliminate that overhead (the overhead is actually much less now that the language objects are not cloned).
> subqueries are not supported anywhere other than where and select clauses of querycommands
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-82
> URL: https://jira.jboss.org/jira/browse/TEIID-82
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 6.x
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 6.1.0
>
>
> Defect Tracker #23760: Subqueries in other place, for example, delete, update, and procedure if statements, and join criteria do not support subqueries in criteria. If this cannot be worked for 5.6, then validations should be added so that invalid subqueries are detected.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-82?page=com.atlassian.jira.plugi... ]
Steven Hawkins reassigned TEIID-82:
-----------------------------------
Assignee: Steven Hawkins
> subqueries are not supported anywhere other than where and select clauses of querycommands
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-82
> URL: https://jira.jboss.org/jira/browse/TEIID-82
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 6.x
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 6.1.0
>
>
> Defect Tracker #23760: Subqueries in other place, for example, delete, update, and procedure if statements, and join criteria do not support subqueries in criteria. If this cannot be worked for 5.6, then validations should be added so that invalid subqueries are detected.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-82?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-82:
-------------------------------------
Removed the link to JBEDSP-928. It's defect line needs to be broken into two paths
1. Non-corrleated non-set subquery evaluation prior to pushdown for all command types.
2. Row based execution of updates (virtual and even physical), which is needed in situations where the update or delete criteria / update set clause contain expressions that cannot be pushed or handled by our update procedure logic.
> subqueries are not supported anywhere other than where and select clauses of querycommands
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-82
> URL: https://jira.jboss.org/jira/browse/TEIID-82
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 6.x
> Reporter: Steven Hawkins
> Fix For: 6.1.0
>
>
> Defect Tracker #23760: Subqueries in other place, for example, delete, update, and procedure if statements, and join criteria do not support subqueries in criteria. If this cannot be worked for 5.6, then validations should be added so that invalid subqueries are detected.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-82?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-82:
--------------------------------
Fix Version/s: 6.1.0
(was: 6.2.0)
> subqueries are not supported anywhere other than where and select clauses of querycommands
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-82
> URL: https://jira.jboss.org/jira/browse/TEIID-82
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 6.x
> Reporter: Steven Hawkins
> Fix For: 6.1.0
>
>
> Defect Tracker #23760: Subqueries in other place, for example, delete, update, and procedure if statements, and join criteria do not support subqueries in criteria. If this cannot be worked for 5.6, then validations should be added so that invalid subqueries are detected.
--
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