[
https://issues.apache.org/jira/browse/TEPHRA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Poorna Chandra updated TEPHRA-138:
----------------------------------
Fix Version/s: (was: 0.7.1)
> Improve change set computation for row and column family deletes
> ----------------------------------------------------------------
>
> Key: TEPHRA-138
> URL: https://issues.apache.org/jira/browse/TEPHRA-138
> Project: Tephra
> Issue Type: Improvement
> Components: hbase-compat-0.96, hbase-compat-0.98, hbase-compat-1.0,
> tephra-hbase-compat-1.0-cdh, tephra-hbase-compat-1.1
> Reporter: Poorna Chandra
> Assignee: Poorna Chandra
>
> When a row or a column family is deleted, TransactionAwareHTable records the
> change set at column level instead of just recording the change set at row or
> column family level.
> This does not let us distinguish between cases where a complete row or a
> column family gets deleted v/s deleting all existing columns of a row or a
> column family. This leads to ignoring conflicts like the following -- a new
> column getting added to a row when another transaction with the same row
> getting deleted is in progress.
> Also, the current implementation involves an unnecessary Get call to fetch
> all columns of a row or a column family on a delete.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
