[
https://issues.apache.org/jira/browse/TEZ-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073860#comment-14073860
]
Siddharth Seth commented on TEZ-1304:
-------------------------------------
Spoke to Bikas offline. I was hoping to re-use all the logic in DAGlient by
just changing the connection (i.e. either RPC based or a direct isntance) -
didn't realize, however, that DAGClient makes use of YarnClient internally.
Having FrameworkClient abstract YARN methods only seems like the way to go - so
that it can be used in both TezClient and DAGClient. Later, we should be able
to abstract out the DAG connection functionality separately - so that the logic
can be applied to an RPC based instance or a local instance.
[~jeagles] - sorry about that. Is this something you can look at changing, to
have the framework client abstract Yarn only (Creating an alternate
implementation of YarnClient would've been an option - but that seems to have
way too many interfaces - and I don't believe it's meant to be implemented
outside of YARN)
> Create execution underlying framework abstraction layer
> -------------------------------------------------------
>
> Key: TEZ-1304
> URL: https://issues.apache.org/jira/browse/TEZ-1304
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Attachments: TEZ-1304-v1.patch, TEZ-1304-v2.patch
>
>
> Continuing in the direction of hiding the internals of the execution
> framework, this patch aims at abstracting it away from the tez client
> implementation. This will further ease the addition of other execution
> frameworks such as Tez Local Mode.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
