hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16108) RowCounter should support multiple key ranges
Date Fri, 22 Jul 2016 17:15:21 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389850#comment-15389850
] 

Hudson commented on HBASE-16108:
--------------------------------

FAILURE: Integrated in HBase-0.98-matrix #375 (See [https://builds.apache.org/job/HBase-0.98-matrix/375/])
HBASE-16108 RowCounter should support multiple key ranges (Konstantin (apurtell: rev 10e06ca618e5ef809ea88d04e553d534e2327ec9)
* hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/RowCounter.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestRowCounter.java


> 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
>             Fix For: 2.0.0, 1.4.0, 0.98.21
>
>         Attachments: HBASE-16108.branch-1.001.patch, HBASE-16108.master.001.patch, HBASE-16108.master.003.patch,
HBASE-16108.master.004.patch, test_HBASE-16108.log, test_TestTableBasedReplicationSourceManagerImpl.log
>
>
> 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)

Mime
View raw message