[PHOENIX-4360] Prevent System.Catalog from splitting

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 4.13.0
• Fix Version/s: 4.14.0, 5.0.0
• Assignee: Lars Hofhansl
• Reporter: Lars Hofhansl
• Created: 09/Nov/17 01:04
• Updated: 26/Jul/18 01:14
• Resolved: 22/Nov/17 00:02

Description

Just talked to jamestaylor.

It turns out that currently System.Catalog is not prevented from splitting generally, but does not allow splitting within a schema.

In the multi-tenant case that is not good enough. When System.Catalog splits and a base table and view end up in different regions the following can happen:

• DROP CASCADE no longer works for those views
• Adding/removing columns to/from the base table no longer works

Until PHOENIX-3534 is done we should simply prevent System.Catalog from splitting. (just like HBase:meta)
apurtell

Issue Links

• is broken by: HBASE-20111 Able to split region explicitly even on shouldSplit return false from split policy