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

Parent-Child linking rows in System.Catalog break tenant view replication

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 4.11.0, 4.12.0
    • 4.13.0
    • None
    • None

    Description

      PHOENIX-2051 introduced new Parent-Child linking rows to System.Catalog that speed up view deletion. Unfortunately, this breaks assumptions in PHOENIX-3639, which gives a way to replicate tenant views from one cluster to another. (It assumes that all the metadata for a tenant view is owned by the tenant – the linking rows are not.)

      PHOENIX-3639 was a workaround in the first place to the more fundamental design problem that Phoenix places the metadata for both table schemas – which should never be replicated – in the same table and column family as the metadata for tenant views, which should be replicated.

      Note that the linking rows also make it more difficult to ever split these two datasets apart, as proposed in PHOENIX-3520.

      Attachments

        1. PHOENIX-4229.patch
          9 kB
          Geoffrey Jacoby
        2. PHOENIX-4229-v2.patch
          10 kB
          Geoffrey Jacoby
        3. PHOENIX-4229-v3.patch
          11 kB
          Geoffrey Jacoby

        Issue Links

        Activity

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

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment