[
https://issues.apache.org/jira/browse/HBASE-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370658#comment-14370658
]
stack commented on HBASE-13262:
-------------------------------
[~ted_yu] What are you doing in here? [~elserj] and [~jonathan.lawlor] are
working on this. They do all the footwork and then you come in after all is
(near) worked out with a patch?
[~elserj] Do we know when the change came in? What's git blame show? That'd
allow us rule when the breakage started, do you think?
[~larsh]
bq. Not ideal, because of the extra RPC, but it would work in 0.98 unchanged,
and would relieve us from the result sizing.
So 0.98 has the issue too? ([~jonathan.lawlor] seems to indicate not? Maybe I
misread). The plan is to add your patch to 0.98 only? Thanks.
> 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, 0.98.13
>
> Attachments: 13262-0.98-testpatch.txt,
> 13262-tag-length-for-withTags-parameter.txt, regionserver-logging.diff,
> 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)
