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

ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 4.15.0, 5.1.0
    • 4.15.0, 5.1.0, 5.0.1
    • None
    • None

    Description

      PHOENIX-5132 changed the ViewIndexId generation logic to use one sequence per physical view index table, whereas before it had been tenant + physical table. This removed the possibility of a tenant view index and a global view index having colliding ViewIndexIds.

      However, existing Phoenix environments may have already created tenant-owned view index ids using the old sequence, and under PHOENIX-5132 if they create another, its ViewIndexId will got back to MIN_VALUE, which could cause a collision with an existing view index id.

      Attachments

        1. PHOENIX-5138-v4.patch
          31 kB
          Geoffrey Jacoby
        2. PHOENIX-5138-v3.patch
          31 kB
          Geoffrey Jacoby
        3. PHOENIX-5138-v2.patch
          25 kB
          Geoffrey Jacoby
        4. PHOENIX-5138.patch
          26 kB
          Geoffrey Jacoby

        Activity

          People

            gjacoby Geoffrey Jacoby
            gjacoby Geoffrey Jacoby
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 4h 50m
                4h 50m