The scanner api does not support that. You can use multiple scanners to get the same effect. The speed won't be much slower either (in 0.20).
In 0.21 with a new api we will cut down on the number of server roundtrips thus improving the speed even more, On Jun 15, 2009 2:04 AM, "Piotr Praczyk" <[email protected]> wrote: Thanks. I meant something a little different although. By fragment I meant all the rows in the table lying ( in the lexicographiocal order) between the row X and Y. The getScanner calls of HTable allow me to specify such rows. Although I wanted to have a sequence of such ragments : X_1 Y_1 ... X_n Y_n after ending the range X_i Y_i I would like the scanner to jump to X_{i+1} Y_{i+1}. for example lets assume we have a table with rows aa ab ac ad ae ba bb bc bd be n=2 X_1 = aa Y_1 = ac X_2 = bc Y_2 = bd I would like the scanner to return following rows: aa, ab, ac, bc, bd [without using fileters to avoid linear searching]. It seems to be not very difficult to implement it myself, but probably there must be some built-in mechanism since this usage looks like a common one. cheers Piotr 2009/6/15 Ryan Rawson <[email protected]> > And let me follow up a bit... > > The best configuration for a m-r job is to have the # of map ta...
