But what it sounds like you're saying - cleverness with the keys and
organization of the input paths has the possibility to keep the process
as a single job (rather than 3), it'll just be a little "hacky" until
some point down the road when we switch some later version (0.21? 0.22?)
of the API. Ultimately, though, we'll have eliminated the 0.18 mapred.*
libraries.
Is this what you're getting at?
On 5/22/2011 4:49 PM, Sean Owen wrote:
Ah righty -- this exists in the old API doesn't it... even in 0.20.x
But it's deprecated. But it's not deprecated in 0.21+.
Yes I think there's a strong argument to make use of that even if it
is deprecated.
I had in mind the unnecessary use of old .mapred. APIs for simple
Mappers and Reducers.
On Sun, May 22, 2011 at 9:41 PM, Jake Mannix<[email protected]> wrote:
Wait, are you saying that we should force things like matrix multiplication
to become a 3-job process, instead of the current 1-job process?
I thought we've already discussed and decided that moving to 0.20 APIs
where possible should be done, but where it removes functionality and
efficiency, we would allow the old API?
-jake
