You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Chinmay Kulkarni (Jira)" <ji...@apache.org> on 2019/12/21 00:55:08 UTC
[jira] [Closed] (PHOENIX-4799) Write cells using checkAndMutate to
prevent conflicting changes
[ https://issues.apache.org/jira/browse/PHOENIX-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chinmay Kulkarni closed PHOENIX-4799.
-------------------------------------
Bulk closing Jiras for the 4.15.0 release.
> 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
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-4799-v2.patch, PHOENIX-4799-v3.patch, PHOENIX-4799-v4-4.x-HBase-1.3.patch, PHOENIX-4799-v4.patch, PHOENIX-4799-v5-4.x-HBase-1.3.patch, PHOENIX-4799-v5.patch, PHOENIX-4799-v6-4.x-HBase-1.3.patch, PHOENIX-4799-v6.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
(v8.3.4#803005)