[
https://issues.apache.org/jira/browse/TEZ-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15534755#comment-15534755
]
Kuhu Shukla commented on TEZ-3362:
----------------------------------
bq. I am not sure how this works in the hive-llap mode.
This implementation would not work in LLAP world AFAIK. The generic service
plugin design that will follow shortly after this, will move the AMNodeTracker
changes and do scheduler service lookups and node connections for deleting
paths instead of handling specific cases(like it does today), similar to
QueryTracker and similar components in Hive. I need to understand the hybrid
case and how LLAP daemons work. Will look into that starting tomorrow. Welcome
more comments/ideas or pointers on how to model the design for the deletion
service plugin. Thanks a lot!
> Delete intermediate data at DAG level for Shuffle Handler
> ---------------------------------------------------------
>
> Key: TEZ-3362
> URL: https://issues.apache.org/jira/browse/TEZ-3362
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Jonathan Eagles
> Assignee: Kuhu Shukla
> Attachments: TEZ-3362.001.patch, TEZ-3362.002.patch,
> TEZ-3362.003.patch, TEZ-3362.004.patch, TEZ-3362.005.patch
>
>
> Applications like hive that use tez in session mode need the ability to
> delete intermediate data after a DAG completes and while the application
> continues to run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
