[
https://issues.apache.org/jira/browse/HBASE-16108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Ryakhovskiy updated HBASE-16108:
-------------------------------------------
Attachment: HBASE-16108.master.003.patch
Ted, I have added test with 10k rows, and on my rig performance seems to be the
same. But 10k is not actually a "large amount of rows", therefore, I think you
are right and I left old behaviour when one pair of keys is provided:
- when there is no rows, it sets FirstKeyOnlyFilter
- when there is one pair of start-end keys, it sets startRow/stopRow and
FirstKeyOnlyFilter
- when there is more than one pair, it sets MultiRowRangeFilter
patch is attached
> RowCounter should support multiple key ranges
> ---------------------------------------------
>
> Key: HBASE-16108
> URL: https://issues.apache.org/jira/browse/HBASE-16108
> Project: HBase
> Issue Type: Improvement
> Reporter: Geoffrey Jacoby
> Assignee: Konstantin Ryakhovskiy
> Attachments: HBASE-16108.master.001.patch,
> HBASE-16108.master.003.patch
>
>
> Currently, RowCounter only allows a single key range to be used as a filter.
> It would be useful in some cases to be able to specify multiple key ranges
> (or prefixes) in the same job. (For example, counting over a set of Phoenix
> tenant ids in an unsalted table)
> This could be done by enhancing the existing key range parameter to take
> multiple start/stop row pairs. Alternately, a new --row-prefixes option could
> be added, similar to what HBASE-15847 did for VerifyReplication.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
