phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4555) Only mark view as updatable if rows cannot overlap with other updatable views
Date Thu, 25 Jan 2018 19:38:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas D'Silva updated PHOENIX-4555:
------------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: PHOENIX-1508

> 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 Taylor
>            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
(v7.6.3#76005)

Mime
View raw message