Uploaded image for project: 'Tajo'
  1. Tajo
  2. TAJO-1310

Maintaining join filters in join operators

    XMLWordPrintableJSON

    Details

      Description

      Introduction

      A join statement can contain join predicates and join filters.
      Join predicates are evaluated during performing the join operation, while join filters are evaluated on the set of join results.

      Let me consider an example join query as follows:

      default> select n_nationkey from nation left outer join region on n_nationkey = r_regionkey where r_regionkey is null;
      

      In this query, the join predicates and filters are as follows:

      • Join predicates: n_nationkey = r_regionkey
      • Join filters: r_regionkey is null

      Problem

      Currently, in query plans, join filters are handled as selection operators, while join predicates are maintained as member variables of join operators.
      This approach makes the implementation simple, but difficult to find the selection operators corresponding to join operators because they are separately maintained.
      This problem is critical when the logical plan optimizer optimizes the join order of a query statement that contains two or more joins each of that has join filters.

      Solution

      Join filters should be distinguished from selection filters, and maintained in the corresponding join operators. For this, we should add join filtlers to the join expression, the logical join node, and several physical join executors.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jihoonson Jihoon Son
                Reporter:
                jihoonson Jihoon Son
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: