[jira] [Resolved] (DRILL-2327) Upper bound on join's row_count_estimate_factor should be increased to handle expanding joins

["Aman Sinha (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DRILL-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aman Sinha resolved DRILL-2327.
-------------------------------
    Resolution: Fixed

Committed patch in: 02d23cb8d
With reference to previous comment, yes we need to think about how to have better control over individual join's cardinality rather than a global factor. 

> Upper bound on join's row_count_estimate_factor should be increased to handle expanding joins
> ---------------------------------------------------------------------------------------------
>
>                 Key: DRILL-2327
>                 URL: https://issues.apache.org/jira/browse/DRILL-2327
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Query Planning & Optimization
>            Reporter: Aman Sinha
>            Assignee: Aman Sinha
>             Fix For: 0.8.0
>
>         Attachments: 0001-DRILL-2327-Raise-the-max-value-allowed-for-join-s-ca.patch
>
>
> The current bounds for planner.join.row_count_estimate_factor is between 0 to 100.  The default value is 1.0.  This parameter determines the estimated output cardinality of a join.  For hugely expanding joins, this is inadequate and we need to allow substantially larger upper bound. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)