Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-2123

Diverged view prevents schema propagation to the entire view hierarchy

    XMLWordPrintableJSON

    Details

    • Type: Test
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.5.0
    • Labels:
      None

      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.

        Attachments

        1. PHOENIX-2123.patch
          7 kB
          Samarth Jain

          Activity

            People

            • Assignee:
              samarthjain Samarth Jain
              Reporter:
              samarthjain Samarth Jain
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: