You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/07/07 10:40:00 UTC

[jira] [Updated] (FLINK-16809) Support setting CallerContext on YARN deployments

     [ https://issues.apache.org/jira/browse/FLINK-16809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-16809:
-----------------------------------
    Labels: auto-deprioritized-major pull-request-available stale-minor  (was: auto-deprioritized-major pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Support setting CallerContext on YARN deployments
> -------------------------------------------------
>
>                 Key: FLINK-16809
>                 URL: https://issues.apache.org/jira/browse/FLINK-16809
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / YARN
>            Reporter: Qi Zhu
>            Priority: Minor
>              Labels: auto-deprioritized-major, pull-request-available, stale-minor
>
> Now the Spark and hive have the Call Context to meet the HDFS Job Audit requirement.
> I think the flink also should to add it, and in our cluster the flink job may have big pressure to the HDFS, it's will be helpful to find the root job.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)