[
https://issues.apache.org/jira/browse/HBASE-26289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi resolved HBASE-26289.
-----------------------------------
Fix Version/s: 2.4.7
2.3.7
3.0.0-alpha-2
2.5.0
Resolution: Fixed
Thanks [~richardantal]! Pushed to branch-2.3+.
> 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
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.3.7, 2.4.7
>
>
> 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)
