Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-1177 Cost-based query optimization
  3. PHOENIX-1296

Scan entire region when tenant-specific table is analyzed

    XMLWordPrintableJSON

    Details

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

      Description

      Based on the issue you've uncovered (that stats must be updated completely for a region), there's a bit of follow on work needed if an ANALYZE is done on a tenant-specific table. This case will be optimized to only scan and analyze the current tenant's data, however we have to make sure that the entire region(s) containing that tenant's data is scanned (or we'll end up replacing the stats for that region with just the one we calculated for that tenant).

      We should be able to do that based on ScanUtil.isAnalyzeTable(scan) being true in DefaultParallelIteratorRegionSplitter and/or ParallelIterators.

        Attachments

        1. Phoenix-1296_3.patch
          2 kB
          ramkrishna.s.vasudevan
        2. Phoenix-1296_1.patch
          20 kB
          ramkrishna.s.vasudevan

          Activity

            People

            • Assignee:
              ram_krish ramkrishna.s.vasudevan
              Reporter:
              jamestaylor James R. Taylor
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: