[
https://issues.apache.org/jira/browse/TEZ-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073787#comment-14073787
]
Siddharth Seth commented on TEZ-1304:
-------------------------------------
Don't see issues with direct method invocation on the AppMaster. I don't think
we can move all our tests to local mode. Beyond the client - we'll end up
skipping all of the TaskScheduler, ContainerLauncher etc if we do this. System
tests etc, and actual jobs will of-course exercise this code path - but that's
not enough. Some tests to exercise the code path within Tez 'unit' tests will
need to stay - maybe a select set of examples running on the mini cluster,
instead of the entire set.
If only the RPC semantics are being skipped - and everything else remains the
same - is that still an issue ? (This could be achieved by converting the
DAGClient to an interface similar to the umbilical).
> 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)
