[
https://issues.apache.org/jira/browse/HBASE-10354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872920#comment-13872920
]
Enis Soztutar commented on HBASE-10354:
---------------------------------------
Forwarding [~saint....@gmail.com]'s comment from parent jira:
{code}
bq. It is more like a "timeline consistency" rather than the eventual
consistency a-la dynamo.
Let us call it 'timeline consistency' from here on out then while it still in
the inception phase. Let us not allow 'eventually consistent' anywhere near our
lexicon else we will only confuse.
{code}
> Add an API for defining consistency per request
> -----------------------------------------------
>
> Key: HBASE-10354
> URL: https://issues.apache.org/jira/browse/HBASE-10354
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.99.0
>
>
> We should add an API to be able to define the expected consistency level per
> operation. This API should also allow to check whether the results coming
> from a query (get or scan) is stale or not. The defaults should reflect the
> current semantics.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
