[
https://issues.apache.org/jira/browse/HBASE-10247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968837#comment-13968837
]
Vladimir Rodionov commented on HBASE-10247:
-------------------------------------------
I think, there is an easy quick patch / work around which will allow to speed
up reads by going only to MemStore or block cache only:
hint on Get/ Append: something like READ_FASTEST;
{code}
Get get = Get(row)
get.setAttribute(OperationWithAttributes.READ_FASTEST);
{code}
{code}
Append append = ..
append.setAttribute(OperationWithAttributes.READ_FASTEST)
{code}
Unfortunately, Increment does not implements OperationWithAttributes. Why?
> 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)
