As long as you know your keyspace, you should be able to create your own
splits. See TableInputFormatBase for the default implementation (which is
1 input split per region)
On 10/19/12 9:32 AM, "Eric Czech" <[EMAIL PROTECTED]> wrote:
>Is there any way to create an InputSplit for a MapReduce job (reading from
>an HBase table) that guarantees sequential rows with some shared key
>will end up in the same mapper?
>For example, if I have sequential keys like this:
>I want a mapper that will definitely see all the rows with keys that start
>Is there a way to do this?