hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5205) Delete handles deleteFamily incorrectly
Date Mon, 16 Jan 2012 02:11:40 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186649#comment-13186649

Lars Hofhansl commented on HBASE-5205:

I also find that the TS of the Delete's constructor is not used as default for delete{Column|Columns|Family|,
which is *really* confusing.

> Delete handles deleteFamily incorrectly
> ---------------------------------------
>                 Key: HBASE-5205
>                 URL: https://issues.apache.org/jira/browse/HBASE-5205
>             Project: HBase
>          Issue Type: Bug
>          Components: client
>            Reporter: Lars Hofhansl
>            Priority: Minor
> Delete.deleteFamily clears all other markers for the same family.
> That is not correct as some of these other markers might be for a later time.
> That logic should be removed.
> If (really) needed this can be slightly optimized by keeping track of the max TS so far
for each family.
> If both the TS-so-far and the TS of a new deleteFamily request is < LATEST_TIMESTAMP
and the TS-so-far is < deleteFamily marker, then the previous delete marker can be removed.
> I think that might be overkill, as most deletes issued from clients are for LATEST_TIMESTAMP
(which the server translates to the current time).
> I'll have a (one-line) patch soon. Unless folks insist on the optimization I mentioned

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message