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

Use LATEST_TIMESTAMP when UPDATE_CACHE_FREQUENCY is not zero

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.11.0
    • None
    • None

    Description

      For non transactional tables, currently with UPDATE_CACHE_FREQUENCY, we'll use LATEST_TIMESTAMP most of the time, until the cached entity expires, in which case we'll use the server timestamp. This seems a bit strange and inconsistent. Instead (for non transactional tables), we should always use LATEST_TIMESTAMP if UPDATE_CACHE_FREQUENCY is non zero, with the exception of the corner case for UPSERT SELECT and DELETE where the same table is being read and written to (see changes to FromCompiler for PHOENIX-3823).

      Attachments

        1. PHOENIX-3907-v4.patch
          5 kB
          Thomas D'Silva
        2. PHOENIX-3907-v3.patch
          5 kB
          Thomas D'Silva
        3. PHOENIX-3907-v2.patch
          3 kB
          Thomas D'Silva
        4. PHOENIX-3907.patch
          3 kB
          Thomas D'Silva

        Activity

          People

            tdsilva Thomas D'Silva
            jamestaylor James R. Taylor
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: