[
https://issues.apache.org/jira/browse/HBASE-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242094#comment-13242094
]
He Yongqiang commented on HBASE-5674:
-------------------------------------
I use the term 'researchy' as it is mentioned so in one email thread. refer to
http://osdir.com/ml/general/2012-03/msg52707.html I have no idea how this term
come up.
bq. 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.
So are you referring this as conflicting with your 'hardcore production worthy
platform' goal?
> 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
