Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 85818200C00 for ; Wed, 18 Jan 2017 23:04:52 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 841DE160B43; Wed, 18 Jan 2017 22:04:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C9D73160B22 for ; Wed, 18 Jan 2017 23:04:51 +0100 (CET) Received: (qmail 9583 invoked by uid 500); 18 Jan 2017 22:04:51 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 9572 invoked by uid 99); 18 Jan 2017 22:04:50 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jan 2017 22:04:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8E0AF18066C for ; Wed, 18 Jan 2017 22:04:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id vx9GYkO2nrib for ; Wed, 18 Jan 2017 22:04:49 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E62795FDC3 for ; Wed, 18 Jan 2017 22:04:48 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 75EDAE0309 for ; Wed, 18 Jan 2017 22:04:27 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5EF7220D39 for ; Wed, 18 Jan 2017 22:04:26 +0000 (UTC) Date: Wed, 18 Jan 2017 22:04:26 +0000 (UTC) From: "Michael Axiak (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-17486) Tighten the contract for batch client methods MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 18 Jan 2017 22:04:52 -0000 [ https://issues.apache.org/jira/browse/HBASE-17486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Axiak updated HBASE-17486: ---------------------------------- Attachment: HBASE-17486.patch > Tighten the contract for batch client methods > --------------------------------------------- > > Key: HBASE-17486 > URL: https://issues.apache.org/jira/browse/HBASE-17486 > Project: HBase > Issue Type: Bug > Components: API > Reporter: Michael Axiak > Priority: Trivial > Attachments: HBASE-17486.patch > > > Right now, the API documentation for Table#get(List) and Table#batch(List, Result[]) both leave open the possibility for the ordering of the result array to be independent of the input actions. > In at least the batch method case, ordering of the result array is important in order to know which partial requests failed in the event of an exception. Since that contact is required in the batch case, I think it should be extended to the get(List) case as well to make the API easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)