[jira] [Updated] (IGNITE-15054) Use statistics for joins

["Alexander Belyak (Jira)" <ji...@apache.org>]

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

Alexander Belyak updated IGNITE-15054:
--------------------------------------
    Description: 
Optimize join selectivity estimation using collected underlying tables statistics. Mostly, it's about equals conditions on join: for common cases when tbl1.col1 = tbl2.col2 presented and statistics available for both columns - optimizer can use additional conditions like (col1.maxValue >= col2.minValue and col1.minValue <= col2.maxValue).

For example: col1 contains numbers from 1 to 10 while col2 contains numbers from 1 to 100. So we can expect that only 10% of rows in tbl2 were selected.

It's all just a hypothetical option to dig in.

  was:Optimize join selectivity estimation using collected underlying tables statistics.


> Use statistics for joins
> ------------------------
>
>                 Key: IGNITE-15054
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15054
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Alexander Belyak
>            Assignee: Alexander Belyak
>            Priority: Major
>
> Optimize join selectivity estimation using collected underlying tables statistics. Mostly, it's about equals conditions on join: for common cases when tbl1.col1 = tbl2.col2 presented and statistics available for both columns - optimizer can use additional conditions like (col1.maxValue >= col2.minValue and col1.minValue <= col2.maxValue).
> For example: col1 contains numbers from 1 to 10 while col2 contains numbers from 1 to 100. So we can expect that only 10% of rows in tbl2 were selected.
> It's all just a hypothetical option to dig in.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)