isidentical opened a new pull request, #3848:
URL: https://github.com/apache/arrow-datafusion/pull/3848

   # Which issue does this PR close?
   
   <!--
   We generally require a GitHub issue to be filed for all bug fixes and 
enhancements and this helps us generate change logs for our releases. You can 
link an issue to this PR using the GitHub syntax. For example `Closes #123` 
indicates that this PR will close issue #123.
   -->
   
   Closes #3802 .
   
    # Rationale for this change
   <!--
    Why are you proposing this change? If this is already explained clearly in 
the issue then this section is not needed.
    Explaining clearly why changes are proposed helps reviewers understand your 
changes and offer better suggestions for fixes.  
   -->
   When we know for a fact that an inner join is disjoint, we can estimate the 
cardinality of an inner join with (at least) one disjoint column as `0`. From 
there, we can derive the cardinality of a left/right and full outer joins.
   
   # What changes are included in this PR?
   <!--
   There is no need to duplicate the description in the issue here but it is 
sometimes worth providing a summary of the individual changes in this PR.
   -->
   We now take an `is_exact` flag in `estimate_join_cardinality` which is only 
`true` when both left and right are originating directly from table providers 
(which might change in the future if we collect more statistics during 
materialization points both in DF and Ballista, and somehow adaptively optimize 
the parent plans according to that). If that `is_exact` flag is true and if we 
identify a disjoint column when calculating the inner join cardinality, we now 
infer the cardinality of an inner join as 0. 
   
   Since the cardinality of left/right/full outer joins can be derived from the 
inner join's cardinality (e.g. a disjoint left outer join would result with the 
number of rows from the left side), this PR also adds support for inferring 
their cardinality. 
   
   # Are there any user-facing changes?
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   No.
   
   <!--
   If there are any breaking changes to public APIs, please add the `api 
change` label.
   -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to