> >> 3. Another idea might be create separate seq files for chunk of >> records and make them non-splittable, ensuring that they go to a >> single mapper. Assuming I can get away with this, see any pros/cons >> with that approach? > > Separate sequence files would require the least amount of custom code. >
Thanks for the response, Joey. So, if I were to do the above, I would still need a custom record reader to put all the keys and values together, right? Thanks, Tom -- =================== Skybox is hiring. http://www.skyboximaging.com/careers/jobs
