[GitHub] incubator-omid pull request #13: [OMID-74] Efficient column family deletion ...

[ohadshacham]

GitHub user ohadshacham opened a pull request:

https://github.com/apache/incubator-omid/pull/13

[OMID-74] Efficient column family deletion in Row level conflict analysis

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.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ohadshacham/incubator-omid 
FamilyDeletionTombstone-squash

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-omid/pull/13.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #13


commit 35ba4c79b4d3f713c6c38f791d5898f778153e2a
Author: Ohad Shacham 
Date:   2017-07-27T13:12:31Z

[OMID-74] Efficient column family deletion in Row level conflict analysis
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.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OMID-74:


GitHub user ohadshacham opened a pull request:

https://github.com/apache/incubator-omid/pull/13

[OMID-74] Efficient column family deletion in Row level conflict analysis

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.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ohadshacham/incubator-omid 
FamilyDeletionTombstone-squash

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-omid/pull/13.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #13


commit 35ba4c79b4d3f713c6c38f791d5898f778153e2a
Author: Ohad Shacham 
Date:   2017-07-27T13:12:31Z

[OMID-74] Efficient column family deletion in Row level conflict analysis
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.




> 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: New Feature
>Reporter: Ohad Shacham
>
> 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
(v6.4.14#64029)

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

[Ohad Shacham (JIRA)]

Ohad Shacham created OMID-74:


 Summary: 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: New Feature
Reporter: Ohad Shacham


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
(v6.4.14#64029)