[jira] [Issue Comment Edited] (HBASE-5674) add support in HBase to overwrite hbase timestamp to a version number during major compaction

["Mikhail Bautin (Issue Comment Edited) (JIRA)" <ji...@apache.org>]

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

Mikhail Bautin edited comment on HBASE-5674 at 4/6/12 9:15 PM:
---------------------------------------------------------------

Thanks Matt and stack for the point out of 4676. Yeah, we are very very interested in the work that is going on HBase-4676.
                
      was (Author: he yongqiang):
    Thanks Matt and stack for the point out of 4676. Yeah, we are very very interested in the work that is going on HBase-4767.
                  
> add support in HBase to overwrite hbase timestamp to a version number during major compaction
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5674
>                 URL: https://issues.apache.org/jira/browse/HBASE-5674
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: He Yongqiang
>            Assignee: He Yongqiang
>
> Right now, a millisecond-level timestamp is attached to every record. 
> In our case, we only need a version number (mostly it will be just zero etc). A millisecond timestamp is too heavy to carry. We should add support to overwrite it to zero during major compaction. 
> KVs before major compaction will remain using system timestamp. And this should be configurable, so that we should not mess up if the hbase timestamp is specified by application.

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