[ https://issues.apache.org/jira/browse/HBASE-10247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092247#comment-14092247 ]
Lars Hofhansl commented on HBASE-10247: --------------------------------------- I think we should get at the user facing changes in 1.0. [~enis]. Then throughout the 1.0 cycle (or for later versions) we can work in implementing the actual optimizations. A world without major compactions might be possible for table where clients no longer define timestamps (or where client always produce monotonically increasing timestamps). > Client promises about timestamps > -------------------------------- > > Key: HBASE-10247 > URL: https://issues.apache.org/jira/browse/HBASE-10247 > Project: HBase > Issue Type: Brainstorming > Reporter: Lars Hofhansl > Priority: Minor > > This is to start a discussion about timestamp promises declared per table of > CF. > For example if a client promises only monotonically increasing timestamps (or > no custom set timestamps) and VERSIONS=1, we can aggressively and easily > remove old versions of the same row/fam/col from the memstore before we > flush, just by supplying a comparator that ignores the timestamp (i.e. two KV > just differing by TS would be considered equal). > That would increase the performance of counters significantly. -- This message was sent by Atlassian JIRA (v6.2#6252)