[
https://issues.apache.org/jira/browse/HBASE-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365872#comment-14365872
]
Jonathan Lawlor commented on HBASE-13262:
-----------------------------------------
bq. Is this a different issue? Should we create a subtask and fix it in 1.0.1?
It appears as though this problem wasn't "caused" by HBASE-11544 but made more
readily reproducible (i.e. the issue already existed, it's just that the
default configuration changes introduced by HBASE-11544 make it occur without
any additional configuration required). I believe this is the case because if
you do the reverse and use the branch-1.0 default values in branch-1+ the issue
does not occur:
{code}
Scan scan = new Scan();
// Configure scan to use branch-1.0 default values
scan.setMaxResultSize(2 * 1024 * 1024);
scan.setCaching(100);
...
{code}
> 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
>
>
> 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)
