[
https://issues.apache.org/jira/browse/HBASE-10247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13969034#comment-13969034
]
Vladimir Rodionov commented on HBASE-10247:
-------------------------------------------
{quote}
It's also bigger than just the memstore. When HFile history corresponds to the
history of its contents, we can start scanning HFiles in order of age (not even
seeking later HFiles unless we didn't find what we are looking for in newer
HFiles).
{quote}
I think [~lhofhansl] is referring to custom compaction into serious of
non-overlapping by date range sorted (of course) HFile's. We have
https://issues.apache.org/jira/browse/PHOENIX-914 for that already.
> 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)
