Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-1674 Snapshot isolation transaction support through Tephra
  3. PHOENIX-2478

Rows committed in transaction overlapping index creation are not populated

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.7.0
    • None
    • None

    Description

      For a reproducible case, see IndexIT.testCreateIndexAfterUpsertStarted() and the associated FIXME comments for PHOENIX-2446.

      The case that is failing is when a commit starts before an index exists, but commits after the index build is completed. For transactional data, this is problematic because the index gets a timestamp after the commit of the data table mutation and thus these mutations won't be seen during the commit. Also, when the index is being built, the data hasn't yet been committed and thus won't be part of the initial index build.

      Attachments

        1. PHOENIX-2478.patch
          39 kB
          James R. Taylor
        2. PHOENIX-2478_v4.patch
          41 kB
          James R. Taylor
        3. PHOENIX-2478_v3.patch
          41 kB
          James R. Taylor
        4. PHOENIX-2478_v2.patch
          41 kB
          James R. Taylor
        5. PHOENIX-2478_addendum4.patch
          33 kB
          James R. Taylor
        6. PHOENIX-2478_addendum3.patch
          1 kB
          James R. Taylor
        7. PHOENIX-2478_addendum2.patch
          11 kB
          James R. Taylor
        8. PHOENIX-2478_addendum.patch
          43 kB
          James R. Taylor

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: