[ https://issues.apache.org/jira/browse/PHOENIX-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791301#comment-17791301 ]
ASF GitHub Bot commented on PHOENIX-4555: ----------------------------------------- virajjasani commented on PR #1704: URL: https://github.com/apache/phoenix/pull/1704#issuecomment-1832644567 Let me keep this here for reference, we can also contribute this later as separate commit. Patch to run BackwardCompatibilityIT locally: ``` diff --git a/phoenix-core/src/it/resources/compatible_client_versions.json b/phoenix-core/src/it/resources/compatible_client_versions.json index 2cb449015..037289bce 100644 - > Only mark view as updatable if rows cannot overlap with other updatable views > ----------------------------------------------------------------------------- > > Key: PHOENIX-4555 > URL: https://issues.apache.org/jira/browse/PHOENIX-4555 > Project: Phoenix > Issue Type: Sub-task > Reporter: James R. Taylor > Assignee: Jing Yu > Priority: Major > > We'll run into issues if updatable sibling views overlap with each other. For > example, say you have the following hierarchy: > T (A, B, C) > V1 (D, E) FROM T WHERE A = 1 > V2 (F, G) FROM T WHERE A = 1 and B = 2 > In this case, there's no way to update both V1 and v2 columns. Secondary > indexes wouldn't work either, if you had one on each V1 & V2. > We should restrict updatable views to > - views that filter on PK column(s) > - sibling views filter on same set of PK column(s) -- This message was sent by Atlassian Jira (v8.20.10#820010)