hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Liochon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10354) Add an API for defining consistency per request
Date Sat, 01 Feb 2014 09:34:08 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888501#comment-13888501

Nicolas Liochon commented on HBASE-10354:

bq. But I think we should carry it over the PB Result as well
I agree. 3 reasons for this:
1) This will be simpler for other clients
2) It will allow to have immutable Result objects (outside of the adapter layer), hence we
will be able to share the objects again
3) Sending multiple calls is expensive (more calls to send, more calls to cancel). If the
primary is under recovery, we could answer to the get requests with a 'stale' status. Then
the client would not have to go to the secondary. This would be available even w/o secondary
replica as well.

> 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
>         Attachments: hbase-10354_v1.patch
> 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

View raw message