AMConfiguration Necessity

[Chen He <ai...@gmail.com>]

I am curious why we need the AMConfiguration class in Tez. It has some
duplicated

We have already had TezConfiguration and YarnConfiguration. It may not be
convenient to have so many configuration files.

To simplify the work on user side. How about we merge AMConfiguration into
TezConfiguration?

Regards!

Chen

Re: AMConfiguration Necessity

[Hitesh Shah <hi...@apache.org>]

Hello Chen, 

If you are referring to org.apache.tez.client. AMConfiguration, it is not really a Configuration object. If you look more into it, it effectively governs the construction of the AM's container as well as how the application is submitted to YARN i.e. queue info for YARN
and local resources, env, credentials, etc for the application submission context. 

I agree that we have a few conf objects in there which need to be sorted out but I am not sure how you would take the above information and put it into TezConfiguration without going through a bunch of serializations/base85 encodes, etc. 

thanks
-- Hitesh

On Mar 3, 2014, at 2:55 PM, Chen He wrote:

> I am curious why we need the AMConfiguration class in Tez. It has some
> duplicated
> 
> We have already had TezConfiguration and YarnConfiguration. It may not be
> convenient to have so many configuration files.
> 
> To simplify the work on user side. How about we merge AMConfiguration into
> TezConfiguration?
> 
> Regards!
> 
> Chen