[JBoss JIRA] Created: (TEIID-1335) Customer requesting the ability to make query planner always create dependent joins.
5:01 p.m.
Customer requesting the ability to make query planner always create dependent joins.
------------------------------------------------------------------------------------
Key: TEIID-1335
URL: https://jira.jboss.org/browse/TEIID-1335
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Nike is finding that the query planner often chooses to use a non-dependent join plan,
even when cost statistics have been gathered on all source systems and a dependent plan
would perform much better.
I've showed them how to use option makedep to force a dependent join scenario.
However, it requires careful analysis of each query to setup the proper makedep
parameters, and may not be feasible when working with hibernate as the client.
Thus, they ask: is there any way to tell the query planner to always use dependent join
for every join, no matter what.
--
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
5:01 p.m.
New subject: [JBoss JIRA] Updated: (TEIID-1335) Customer requesting the ability to make query planner always create dependent joins.
[
https://jira.jboss.org/browse/TEIID-1335?page=com.atlassian.jira.plugin.s...
]
Debbie Steigner updated TEIID-1335:
-----------------------------------
Description:
Customer is finding that the query planner often chooses to use a non-dependent join plan,
even when cost statistics have been gathered on all source systems and a dependent plan
would perform much better.
I've showed them how to use option makedep to force a dependent join scenario.
However, it requires careful analysis of each query to setup the proper makedep
parameters, and may not be feasible when working with hibernate as the client.
Thus, they ask: is there any way to tell the query planner to always use dependent join
for every join, no matter what.
was:
Nike is finding that the query planner often chooses to use a non-dependent join plan,
even when cost statistics have been gathered on all source systems and a dependent plan
would perform much better.
I've showed them how to use option makedep to force a dependent join scenario.
However, it requires careful analysis of each query to setup the proper makedep
parameters, and may not be feasible when working with hibernate as the client.
Thus, they ask: is there any way to tell the query planner to always use dependent join
for every join, no matter what.
Customer requesting the ability to make query planner always create
dependent joins.
------------------------------------------------------------------------------------
Key: TEIID-1335
URL: https://jira.jboss.org/browse/TEIID-1335
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Customer is finding that the query planner often chooses to use a non-dependent join
plan, even when cost statistics have been gathered on all source systems and a dependent
plan would perform much better.
I've showed them how to use option makedep to force a dependent join scenario.
However, it requires careful analysis of each query to setup the proper makedep
parameters, and may not be feasible when working with hibernate as the client.
Thus, they ask: is there any way to tell the query planner to always use dependent join
for every join, no matter what.
--
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
6:32 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1335) Customer requesting the ability to make query planner always create dependent joins.
[
https://jira.jboss.org/browse/TEIID-1335?page=com.atlassian.jira.plugin.s...
]
Steven Hawkins commented on TEIID-1335:
---------------------------------------
I would rather see this as a costing or cost tuning issue. We have some built-in
assumptions about source performance when issuing the dependent side queries that may not
match their particular performance characteristics. If they can provide us with examples
including costing information, if keys are used, sample timings, etc. then I can look at
changing the assumptions or adding tuning parameters to the translator properties.
Customer requesting the ability to make query planner always create
dependent joins.
------------------------------------------------------------------------------------
Key: TEIID-1335
URL: https://jira.jboss.org/browse/TEIID-1335
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Customer is finding that the query planner often chooses to use a non-dependent join
plan, even when cost statistics have been gathered on all source systems and a dependent
plan would perform much better.
I've showed them how to use option makedep to force a dependent join scenario.
However, it requires careful analysis of each query to setup the proper makedep
parameters, and may not be feasible when working with hibernate as the client.
Thus, they ask: is there any way to tell the query planner to always use dependent join
for every join, no matter what.
--
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
9:06 p.m.
New subject: [JBoss JIRA] Resolved: (TEIID-1335) Customer requesting the ability to make query planner always create dependent joins.
[
https://issues.jboss.org/browse/TEIID-1335?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1335.
-----------------------------------
Resolution: Rejected
Marking as rejected since we will not work the issue as stated (forcing dependent joins
without a hint). If more information could be provided, then we could work this as a
costing/planning issue.
Customer requesting the ability to make query planner always create
dependent joins.
------------------------------------------------------------------------------------
Key: TEIID-1335
URL: https://issues.jboss.org/browse/TEIID-1335
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Customer is finding that the query planner often chooses to use a non-dependent join
plan, even when cost statistics have been gathered on all source systems and a dependent
plan would perform much better.
I've showed them how to use option makedep to force a dependent join scenario.
However, it requires careful analysis of each query to setup the proper makedep
parameters, and may not be feasible when working with hibernate as the client.
Thus, they ask: is there any way to tell the query planner to always use dependent join
for every join, no matter what.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
New subject: [JBoss JIRA] Closed: (TEIID-1335) Customer requesting the ability to make query planner always create dependent joins.
[
https://issues.jboss.org/browse/TEIID-1335?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1335.
---------------------------------
Customer requesting the ability to make query planner always create
dependent joins.
------------------------------------------------------------------------------------
Key: TEIID-1335
URL: https://issues.jboss.org/browse/TEIID-1335
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Customer is finding that the query planner often chooses to use a non-dependent join
plan, even when cost statistics have been gathered on all source systems and a dependent
plan would perform much better.
I've showed them how to use option makedep to force a dependent join scenario.
However, it requires careful analysis of each query to setup the proper makedep
parameters, and may not be feasible when working with hibernate as the client.
Thus, they ask: is there any way to tell the query planner to always use dependent join
for every join, no matter what.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4842
days inactive
4988
days old
4 comments
2 participants
participants (2)
-
Debbie Steigner (JIRA) -
Steven Hawkins (JIRA)