You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2015/07/15 21:35:04 UTC
[jira] [Created] (PHOENIX-2123) Diverged view prevents schema
propagation to the entire view hierarchy
Samarth Jain created PHOENIX-2123:
-------------------------------------
Summary: Diverged view prevents schema propagation to the entire view hierarchy
Key: PHOENIX-2123
URL: https://issues.apache.org/jira/browse/PHOENIX-2123
Project: Phoenix
Issue Type: Test
Reporter: Samarth Jain
Assignee: Samarth Jain
This code in MetadataEndPointImpl
{code}
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);
}
{code}
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)