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

Optimize metadata cache lookup of global tables using a tenant specific connection

Attach filesAttach ScreenshotVotersStop watchingWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 4.14.2
    • 4.15.0, 5.1.0
    • None
    • None

    Description

      If we use a teanant specific connection to look up a global table we always make an rpc to the server even if the UPDATE_CACHE_FREQUENCY is set on the table.

      Attachments

        1. diff.patch
          8 kB
          Thomas D'Silva
        2. PHOENIX-5403.patch
          9 kB
          Thomas D'Silva
        3. PHOENIX-5403-v2.patch
          11 kB
          Thomas D'Silva
        4. PHOENIX-5403-v3.patch
          12 kB
          Thomas D'Silva
        5. PHOENIX-5403-v4.patch
          13 kB
          Thomas D'Silva
        6. PHOENIX-5403-v5.patch
          13 kB
          Thomas D'Silva

        Issue Links

        causes

        Bug - A problem which impairs or prevents the functions of the product. PHOENIX-6534 Upgrades from pre 4.10 versions are broken

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tdsilva Thomas D'Silva
            tdsilva Thomas D'Silva
            Votes:
            0 Vote for this issue
            Watchers:
            3 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment