[ 
https://issues.apache.org/jira/browse/HBASE-30464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Somogyi updated HBASE-30464:
----------------------------------
    Fix Version/s: hbase-operator-tools-1.4.0
     Release Note: Updated exit code behavior to return `1` on incorrect 
command-line usage or invalid arguments (previously returned `0`).
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

Merged. Thanks for the review, [~paksyd].

> [hbase-operator-tools] TableReporter --limit scans only one row per region
> --------------------------------------------------------------------------
>
>                 Key: HBASE-30464
>                 URL: https://issues.apache.org/jira/browse/HBASE-30464
>             Project: HBase
>          Issue Type: Bug
>          Components: hbase-operator-tools
>            Reporter: Peter Somogyi
>            Assignee: Peter Somogyi
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: hbase-operator-tools-1.4.0
>
>
> The --limit option of TableReporter has the check reversed: if (limit >= 0 && 
> count <= limit) With limit N, each region's scan stops after its first row. 
> With limit 0, the whole region is scanned.
> Since the scan uses setAllowPartialResults(true), it also counted each 
> partial Result as a row.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to