[
https://issues.apache.org/jira/browse/TEZ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated TEZ-4682:
------------------------------
Description:
The point here is to have a Tez AM image that runs the *DAGAppMaster* process.
The POC should contain and utilize the following:
1. Dockerfile to build such an image
2. Docker container started from that image
3. DAGAppMaster's RPC port exposed so that clients (e.g. Hive) can submit a DAG
4. Extension point for plugins: this is tricky, hive LLAP uses its own plugin
jars inside Tez AM, however Tez cannot depend on anything that is Hive
specific, so the TezAM container should be able mount a path, from where custom
jars can be added to the classpath.
was:
The point here is to have a Tez AM image that runs the *DAGAppMaster* process.
The POC should contain the following:
1. Dockerfile to build such an image
2.
> [Cloud] Tez AM docker image
> ---------------------------
>
> Key: TEZ-4682
> URL: https://issues.apache.org/jira/browse/TEZ-4682
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: László Bodor
> Priority: Major
>
> The point here is to have a Tez AM image that runs the *DAGAppMaster*
> process. The POC should contain and utilize the following:
> 1. Dockerfile to build such an image
> 2. Docker container started from that image
> 3. DAGAppMaster's RPC port exposed so that clients (e.g. Hive) can submit a
> DAG
> 4. Extension point for plugins: this is tricky, hive LLAP uses its own plugin
> jars inside Tez AM, however Tez cannot depend on anything that is Hive
> specific, so the TezAM container should be able mount a path, from where
> custom jars can be added to the classpath.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
