[teiid-issues] [JBoss JIRA] Updated: (TEIID-1335) Customer requesting the ability to make query planner always create dependent joins.

[Debbie Steigner (JIRA)]

     [ https://jira.jboss.org/browse/TEIID-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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