[PHOENIX-3955] Ensure KEEP_DELETED_CELLS, REPLICATION_SCOPE, and TTL properties stay in sync between the physical data table and index tables

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.15.0, 5.1.0
• Assignee: Chinmay Kulkarni
• Reporter: Samarth Jain
• Created: 16/Jun/17 22:59
• Updated: 21/Dec/19 00:54
• Resolved: 10/Oct/18 23:29

Description

We need to make sure that indexes inherit the REPLICATION_SCOPE, KEEP_DELETED_CELLS and TTL properties from the base table. Otherwise we can run into situations where the data was removed (or not removed) from the data table but was removed (or not removed) from the index. Or vice-versa. We also need to make sure that any ALTER TABLE SET TTL or ALTER TABLE SET KEEP_DELETED_CELLS statements propagate the properties to the indexes too.

Issue Links

• duplicates: PHOENIX-4667 Create index on a view should return error if any of the REPLICATION_SCOPE/TTL/KEEP_DELETED_CELLS attributes are set
• is related to: PHOENIX-4891 An index should inherit UPDATE_CACHE_FREQUENCY setting from parent table
• links to: GitHub Pull Request #304
• links to: GitHub Pull Request #346