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

Support running multiple transaction providers

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.14.0, 5.0.0
    • None
    • None

    Description

      We should deprecate QueryServices.DEFAULT_TABLE_ISTRANSACTIONAL_ATTRIB and instead have a QueryServices.DEFAULT_TRANSACTION_PROVIDER now that we'll have two transaction providers: Tephra and Omid. Along the same lines, we should add a TRANSACTION_PROVIDER column to SYSTEM.CATALOG and stop using the IS_TRANSACTIONAL table property. For backwards compatibility, we can assume the provider is Tephra if the existing properties are set to true.

      Attachments

        1. PHOENIX-4605_wip1.patch
          95 kB
          James R. Taylor
        2. PHOENIX-4605_wip2.patch
          228 kB
          James R. Taylor
        3. PHOENIX_4605_wip3.patch
          233 kB
          James R. Taylor
        4. PHOENIX-4605_v1.patch
          238 kB
          James R. Taylor
        5. PHOENIX-4605_v2.patch
          263 kB
          James R. Taylor
        6. PHOENIX-4605_v3.patch
          264 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: