[
https://issues.apache.org/jira/browse/TEZ-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073414#comment-14073414
]
Bikas Saha commented on TEZ-1304:
---------------------------------
In conjunction with TEZ-717, I have the following suggestion. Can we restrict
FrameworkClient to just YARN, specifically YARNClient. This way we are actually
only abstracting the underlying execution layer - YARN. All other Tez specific
code paths are exercised as is and without duplication. The FrameworkClient
could be used in TezClient as well as DAGClient to abstract out the remote YARN
cluster piece. Then TezClient and DAGClient could be used as is. Not only does
it remove code duplication but it also assures us that all/identical Tez code
paths are being exercised during tests as would be in real life. The downside
would be using RPC to the local AM but the cost of that should not be
prohibitive. Thoughts?
> 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)
