[PHOENIX-4229] Parent-Child linking rows in System.Catalog break tenant view replication

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.11.0, 4.12.0
• Fix Version/s: 4.13.0
• Assignee: Geoffrey Jacoby
• Reporter: Geoffrey Jacoby
• Created: 25/Sep/17 17:19
• Updated: 03/Nov/17 22:18
• Resolved: 11/Oct/17 18:16

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.

Issue Links

• is broken by: PHOENIX-2051 Link record is in the format CHILD-PARENT for phoenix views and it has to scan the entire table to find the parent suffix.