You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Raghav Aggarwal (Jira)" <ji...@apache.org> on 2026/03/24 08:40:00 UTC

[jira] [Commented] (TEZ-4682) [Cloud] Tez AM docker image

    [ https://issues.apache.org/jira/browse/TEZ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18067947#comment-18067947 ] 

Raghav Aggarwal commented on TEZ-4682:
--------------------------------------

Thanks a lot [~abstractdog] , for your patience during the review, for suggestions and giving me opportunity to contribute to this amazing feature.

> [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
>            Assignee: Raghav Aggarwal
>            Priority: Major
>             Fix For: 1.0.0
>
>          Time Spent: 9.5h
>  Remaining Estimate: 0h
>
> 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)