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 9093B200C86 for ; Wed, 31 May 2017 19:26:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8ECB9160BCB; Wed, 31 May 2017 17:26:08 +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 D5BBB160BC2 for ; Wed, 31 May 2017 19:26:07 +0200 (CEST) Received: (qmail 92478 invoked by uid 500); 31 May 2017 17:26:07 -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 92466 invoked by uid 99); 31 May 2017 17:26:07 -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, 31 May 2017 17:26:07 +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 A2AF7180314 for ; Wed, 31 May 2017 17:26:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id fwWzr4FQCy-j for ; Wed, 31 May 2017 17:26:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 8745E5FB71 for ; Wed, 31 May 2017 17:26:05 +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 CB6B9E0BDE for ; Wed, 31 May 2017 17:26:04 +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 8751E21B59 for ; Wed, 31 May 2017 17:26:04 +0000 (UTC) Date: Wed, 31 May 2017 17:26:04 +0000 (UTC) From: "Karan Mehta (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-18097) Save bandwidth on partial_flag_per_result in ScanResponse proto MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 31 May 2017 17:26:08 -0000 [ https://issues.apache.org/jira/browse/HBASE-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated HBASE-18097: -------------------------------- Summary: Save bandwidth on partial_flag_per_result in ScanResponse proto (was: Client can save 1 RPC call for CloseScannerRequest) > Save bandwidth on partial_flag_per_result in ScanResponse proto > --------------------------------------------------------------- > > Key: HBASE-18097 > URL: https://issues.apache.org/jira/browse/HBASE-18097 > Project: HBase > Issue Type: Improvement > Affects Versions: 1.3.2 > Reporter: Karan Mehta > > Starting version 1.3, HBase automatically closes scanner on server side whenever the results are exhausted and corresponding bits are set in the {{ScanResponse}} proto returned to the client. We can use that info to eliminate the closeScanRequest RPC call, thereby saving 1 RPC per region per scan. This can be particularly useful for tables with more regions. > Also, currently the {{ScanResponse}} proto sends out 1 bit per {{Result}} that it has embeds inside the {{CellScanner}} to indicate if it is partial or not. > {code} > // In every RPC response there should be at most a single partial result. Furthermore, if > // there is a partial result, it is guaranteed to be in the last position of the array. > {code} > According to client, only the last result can be partial, thus this repeated bool can be converted to a bool, thus reducing overhead of serialization and deserialization of the array. This will break wire compatibility therefore this is something to look for in upcoming versions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)