hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amitanand Aiyer (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-6075) Improve delete(Latest-timestamp) performance: consider adding a delete_next type
Date Wed, 23 May 2012 21:19:41 GMT
Amitanand Aiyer created HBASE-6075:

             Summary: Improve delete(Latest-timestamp) performance: consider adding a delete_next
                 Key: HBASE-6075
                 URL: https://issues.apache.org/jira/browse/HBASE-6075
             Project: HBase
          Issue Type: Brainstorming
            Reporter: Amitanand Aiyer
            Priority: Minor

Disclaimer: this will only work correctly if the application is not taking control of the

We have a version of deleteVersion, which deletes the last version, if no specific timestamp
is specified  (i.e. timestamp is left as Long.MAX_VALUE)

On the server side, this translates to deleting the largest timestamped cell in the specified
column. Which entails doing a get, and then a delete.

We don't seem to use this api a whole lot, so not a very high pri task. 

But, for systems that use the api. We might be able to make this much faster (as fast as the
puts) by introducing a new delete type (say DELETE_NEXT_VERSION) that sorts right after put
in the column, and just adding it as a put. The deleteTracker can be updated to keep track
of this delete_next and accordingly delete the nextKV asked for.

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