Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-852

Optimize child/parent foreign key joins

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.0, 3.2.0
    • Labels:
      None

      Description

      Often times a join will occur from a child to a parent. Our current algorithm would do a full scan of one side or the other. We can do much better than that if the HashCache contains the PK (or even part of the PK) from the table being joined to. In these cases, we should drive the second scan through a skip scan on the server side.

        Attachments

        1. 852-4.patch
          83 kB
          Maryann Xue
        2. 852-3.patch
          83 kB
          Maryann Xue
        3. 852-2.patch
          48 kB
          Maryann Xue
        4. 852.patch
          45 kB
          Maryann Xue
        5. PHOENIX-852.patch
          41 kB
          Maryann Xue

          Issue Links

            Activity

              People

              • Assignee:
                maryannxue Maryann Xue
                Reporter:
                jamestaylor James Taylor
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: