You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@omid.apache.org by "Ohad Shacham (JIRA)" <ji...@apache.org> on 2018/03/15 08:35:00 UTC

[jira] [Reopened] (OMID-74) Efficient column family deletion in Row level conflict analysis

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

Ohad Shacham reopened OMID-74:
------------------------------

Currently, the update of the write set is incorrect since the family deletion qualifier needs to be added instead of a row marker. Therefore, I am reopening this Jira to fix this case.

This is crucial since the write set information is needed for adding shadow cells, when transaction successfully commits, and for garbage collection when transaction aborts.

> Efficient column family deletion in Row level conflict analysis
> ---------------------------------------------------------------
>
>                 Key: OMID-74
>                 URL: https://issues.apache.org/jira/browse/OMID-74
>             Project: Apache Omid
>          Issue Type: Sub-task
>            Reporter: Ohad Shacham
>            Assignee: Ohad Shacham
>            Priority: Major
>
> The idea is to use a qualifier to denote that all the columns of a specific family were deleted. 
> Current implementation reads from HBase the entire family and then writes a tombstone to each one of its cells. The new implementation does not need to perform the read and only writes the qualifier to denote that the family was deleted. This is true only for Row level conflict detection since in Cell level we need to read the cells and add these to the write set.



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