Hi,

> So what do you suggest to get unique-id for mapper task with tez
>execution engine?
> 
> conf.get("mapreduce.task.partition");
>
> Is this correct?

Yes, that is correct - but it can only be unique within a Mapper vertex.

Tez plans sort of look like this for complex queries

http://people.apache.org/~gopalv/tpch-plans/q2_minimum_cost_supplier.svg


Every MapTezProcessor there will go from 0-n, for that config parameter.

So all those Map 1, Map 2 ... Map 17 will have a task.partition 0 with the
same <attempt_..._m_000000_0> in the attempt id, because there's no room
for a vertex-id in there.

Cheers,
Gopal







Reply via email to