[
https://issues.apache.org/jira/browse/HBASE-26289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416622#comment-17416622
]
Richárd Antal commented on HBASE-26289:
---------------------------------------
I think the issue is caused because we exit the loop in the middle of the row
here
[https://github.com/apache/hbase/blob/c60adfd13a24f0256681bc0fd6e3a93fd8991280/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java#L692]
Later when we read the next cell for the same row, the count wont be > 0
because of this check
[https://github.com/apache/hbase/blob/c60adfd13a24f0256681bc0fd6e3a93fd8991280/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java#L635]
This means we didn't read the cell because we already read one before (in case
of setMaxResultsPerColumnFamily(1)) but it doesn't mean that there are no more
values.
[https://github.com/apache/hbase/blob/c60adfd13a24f0256681bc0fd6e3a93fd8991280/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java#L766]
> Hbase scan setMaxResultsPerColumnFamily not giving right results
> ----------------------------------------------------------------
>
> Key: HBASE-26289
> URL: https://issues.apache.org/jira/browse/HBASE-26289
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 3.0.0-alpha-1, 2.1.9, 2.2.7, 2.3.6, 2.4.6
> Reporter: Richárd Antal
> Assignee: Richárd Antal
> Priority: Major
>
> scan.setMaxResultsPerColumnFamily(1) is giving less number of row keys
> vs when it is not set in the scan, on a table that has multiple column
> families and multiple qualifier or multiple versions for each cell
> Docs for setMaxResultsPerColumnFamily:
> {code:java}
> /**
> * Set the maximum number of values to return per row per Column Family
> * @param limit the maximum number of values returned / row / CF
> */{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
