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

Optimize child/parent foreign key joins

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 4.2.0, 3.2.0
    • None
    • 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. PHOENIX-852.patch
          41 kB
          Wei Xue
        2. 852-4.patch
          83 kB
          Wei Xue
        3. 852-3.patch
          83 kB
          Wei Xue
        4. 852-2.patch
          48 kB
          Wei Xue
        5. 852.patch
          45 kB
          Wei Xue

        Issue Links

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. PHOENIX-889 Query performance with Join feature is poor

          • Major - Major loss of function.
          • Closed
          links to

          Web Link GitHub Pull Request #7

          Activity

            People

              maryannxue Wei Xue
              jamestaylor James R. Taylor
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: