Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B25517DB1 for ; Thu, 19 Mar 2015 01:04:41 +0000 (UTC) Received: (qmail 84768 invoked by uid 500); 19 Mar 2015 01:04:41 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 84728 invoked by uid 500); 19 Mar 2015 01:04:41 -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 84716 invoked by uid 99); 19 Mar 2015 01:04:41 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Mar 2015 01:04:41 +0000 Date: Thu, 19 Mar 2015 01:04:41 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-13262) ResultScanner doesn't return all rows in Scan MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368268#comment-14368268 ] Andrew Purtell commented on HBASE-13262: ---------------------------------------- bq. This approach wouldn't break 0.98 clients against 1.x; however, it also wouldn't address the underlying problem of the client guessing at what to do based on the characteristics of the {{Result[]}} when it is unaware of the existence of this new field in the protobuf. Given my understanding of the problem, 0.98 clients running against 1.x *could* see this problem, although I have not tested that to confirm it happens. Wire compatibility and a default configuration in 1.0.x that mitigates the problem until a rolling upgrade is completed could be good enough. Additional comment reserved until you come back with results from more digging. > ResultScanner doesn't return all rows in Scan > --------------------------------------------- > > Key: HBASE-13262 > URL: https://issues.apache.org/jira/browse/HBASE-13262 > Project: HBase > Issue Type: Bug > Components: Client > Affects Versions: 2.0.0, 1.1.0 > Environment: Single node, pseduo-distributed 1.1.0-SNAPSHOT > Reporter: Josh Elser > Assignee: Josh Elser > Priority: Blocker > Fix For: 2.0.0, 1.1.0 > > Attachments: testrun_0.98.txt, testrun_branch1.0.txt > > > Tried to write a simple Java client again 1.1.0-SNAPSHOT. > * Write 1M rows, each row with 1 family, and 10 qualifiers (values [0-9]), for a total of 10M cells written > * Read back the data from the table, ensure I saw 10M cells > Running it against {{04ac1891}} (and earlier) yesterday, I would get ~20% of the actual rows. Running against 1.0.0, returns all 10M records as expected. > [Code I was running|https://github.com/joshelser/hbase-hwhat/blob/master/src/main/java/hbase/HBaseTest.java] for the curious. -- This message was sent by Atlassian JIRA (v6.3.4#6332)