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-4799) Write cells using checkAndMutate to prevent conflicting changes
Date Thu, 26 Jul 2018 00:21:00 GMT

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

Thomas D'Silva updated PHOENIX-4799:
------------------------------------
    Attachment: PHOENIX-4799-4.x-HBase-1.3-v2.patch

> Write cells using checkAndMutate to prevent conflicting changes
> ---------------------------------------------------------------
>
>                 Key: PHOENIX-4799
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4799
>             Project: Phoenix
>          Issue Type: Sub-task
>    Affects Versions: 4.15.0, 5.1.0
>            Reporter: Thomas D'Silva
>            Assignee: Thomas D'Silva
>            Priority: Major
>         Attachments: PHOENIX-4799-4.x-HBase-1.3-v2.patch, PHOENIX-4799.patch
>
>
> In order to prevent race conditions when multiple client try to mutate the same column
before sending the request to mutate the column to the server do a checkAndMutate with the
column name being added/dropped. Also:
>  1. When a view is created do a checkAndMutate with the columns in the view where clause.
>  2. When an index on a view is created do a checkAndMutate with the indexed columns.
>  
> To prevent a race condition in the DROP TABLE CASCADE case, when a table is dropped do
a checkAndMutate with the rowkey of the base table name. If a view is created it also does
a checkAndMutate with the same rowkey. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message