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

Cleanup setting of timestamps when collecting and using stats

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 4.2.0, 3.2.0
    • None
    • None

    Description

      We're currently not using the max timestamp that was passed through the Scan when we do an ANALYZE. In the same way, we're not using the client timestamp when we read the stats and cache them on PTable. The tricky thing is what timestamp to use for the stats when a split or compaction occurs, because in those cases we don't have a user supplied timestamp (if they're managing timestamps themselves).

      Attachments

        1. PHOENIX-1321_4.patch
          70 kB
          James R. Taylor

        Activity

          People

            jamestaylor James R. Taylor
            jamestaylor James R. Taylor
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: