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

ASF GitHub Bot commented on OMID-74:
------------------------------------

Github user ebortnik commented on a diff in the pull request:

    https://github.com/apache/incubator-omid/pull/13#discussion_r130566417
  
    --- Diff: 
hbase-client/src/main/java/org/apache/omid/transaction/TTable.java ---
    @@ -333,7 +360,7 @@ public ResultScanner getScanner(Transaction tx, Scan 
scan) throws IOException {
          * @return Filtered KVs belonging to the transaction snapshot
          */
         List<Cell> filterCellsForSnapshot(List<Cell> rawCells, 
HBaseTransaction transaction,
    -                                      int versionsToRequest) throws 
IOException {
    +                                      int versionsToRequest, Map<String, 
List<Cell>> familyDeletionCache) throws IOException {
    --- End diff --
    
    Please explain the last param


> 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)

Reply via email to