[
https://issues.apache.org/jira/browse/HBASE-10354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899528#comment-13899528
]
Hadoop QA commented on HBASE-10354:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12628542/10354.add.patch
against trunk revision .
ATTACHMENT ID: 12628542
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8673//console
This message is automatically generated.
> 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, hbase-10070
>
> Attachments: 10354.add.patch, hbase-10354_v1.patch,
> hbase-10354_v2.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
(v6.1.5#6160)
