hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5674) add support in HBase to overwrite hbase timestamp to a version number during major compaction
Date Fri, 30 Mar 2012 16:26:28 GMT

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

stack commented on HBASE-5674:
------------------------------

@He np.  Thanks for the background.  On a slightly related note, I was going to ask if you'd
been following Matt's work over in hbase-4676.  The compression factor he gets over there
I thought you'd be interested in.
                
> 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

        

Mime
View raw message