[PHOENIX-2123] Diverged view prevents schema propagation to the entire view hierarchy

• Type: Test
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.5.0
• Assignee: Samarth Jain
• Reporter: Samarth Jain
• Created: 15/Jul/15 19:34
• Updated: 21/Nov/15 02:18
• Resolved: 15/Jul/15 20:35

Description

This code in MetadataEndPointImpl

if (view.getBaseColumnCount() == QueryConstants.DIVERGED_VIEW_BASE_COLUMN_COUNT) {
                // if a view has divorced itself from the base table, we don't allow schema changes
                // to be propagated to it.
            	return new MetaDataMutationResult(MutationCode.UNALLOWED_TABLE_MUTATION, EnvironmentEdgeManager.currentTimeMillis(), null);
            }

ends up preventing metadata changes to be propagated to the entire hierarchy. Because of this bug, some views might have the change and some may not which is not good.