Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 30 Mar 2012 05:48:38 +0000 (UTC)
From: "stack (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <861370115.36718.1333086518593.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1839311683.33865.1333044142282.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5674) add support in HBase to overwrite
 hbase timestamp to a version number during major compaction
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

bq. I hope this can be done in open source hbase, and can be pluggable.

Can you do your research w/o requiring that your 'researchy' code be committed to core.  The most of us working on hbase are trying to make it an hardcore production worthy platform.  'Pluggable' and 'research', at least on first blush, sound like distractions from the project objective.

But maybe the research aligns with where hbase is trying to go.  Whats your research on?

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