I assume you know the tradeoff here: If you do depend upon mapper slot # in
your implementation to speed it up, you are losing on code portability in
long term
That said, one way to achieve this is to use the JobConf API:
int partition = jobConf.getInt(JobContext.TASK_PARTITION, -1);
The fra
In Hadoop under the mapred-site.conf I can set the maximum number of mappers.
For the sake of this email I will call the number of concurrent mappers: mapper
slots.
Is it possible to figure out from within the mapper which mapper slot it is
running in?
On this project this is important becau
